On 6/27/11 2:18 PM, "Jeff Johnson" <email@example.com> wrote:
>On Jun 27, 2011, at 1:59 PM, Miller, Vincent (Rick) wrote:
>> On 6/25/11 4:39 AM, "Anders F Björklund" <firstname.lastname@example.org> wrote:
>>> The BSD and Mac ports are currently using 5.2.1, that is the pre-ACID
>> I would be happy with the FreeBSD port of RPM. I did do an install of
>> and it did not install the rpmbuild binary. This was one of the main
>> reasons for downloading and installing from source
>Are you trying to build *.rpm's on FreeBSD? That is
>doable, but the binary *.rpm's produced are likely
>not going to usable anywhere except on FreeBSD (which
>doesn't use rpmbuild) without a fair amount of work.
>What problem are you trying to solve?
The problem being solved is not really a problem. A decision was made
that ops should employ a unified approach to managing software on a
system. By unified approach, I mean issuing the same command to install
something, despite the platform. The task to integrate RPM into FreeBSD
was handed to me.
RPMs that get built on FreeBSD will only be installed in FreeBSD and vice
>> Perhaps I'll setup another VM and give the FreeBSD port another try
>I can turn on my FreeBSD VM which worked with the "%fbsd8x"
>build options in devtool.conf under buildbot's for several
>weeks running "make check if there's really a need.
>You can have the whole VM if you prepared for a 20+ GB VMFusion download.
>I likely can reinstall and redo the entire VM and build RPM from
>a cvs checkout in less time than the download takes.
Don't worry about your FreeBSD VM at the moment. I'm just interested in
the simplest way to get rpm and rpmbuild to function on FreeBSD. If I can
accomplish this with the BSD port, that will likely be the method I use to
I must admit, I am unfamiliar with devtool and devtool.conf. Google
returns lots of results. Is there an official project page for this?
Received on Mon Jun 27 20:39:11 2011