Date: Mon, 15 Feb 2010 17:01:35 -0800 From: Garrett Cooper <yanefbsd@gmail.com> To: Darren Pilgrim <freebsd@bitfreak.org> Cc: ports@freebsd.org Subject: Re: Installing a different PORTVERSION based on OSVERSION? Message-ID: <7d6fde3d1002151701w5b7720few70e474e82458f8bf@mail.gmail.com> In-Reply-To: <4B787718.3040605@bitfreak.org> References: <4B776D6F.10008@bitfreak.org> <20100214180243.GA79050@atarininja.org> <4B7863FE.9040108@bitfreak.org> <7d6fde3d1002141348q1facadd4l5b11b4749379d49f@mail.gmail.com> <4B787718.3040605@bitfreak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Feb 14, 2010 at 2:20 PM, Darren Pilgrim <freebsd@bitfreak.org> wrot=
e:
> Garrett Cooper wrote:
>>
>> =A0 =A0Vendor provided binaries are a fun ball of wax to deal with
>> because you need to have all dependencies come from the same generic
>> pool as the package [/ port] itself, as any
>> =A0 =A0This sounds trivial, but it requires changes to pkg_add (for
>> fetching / installing a particular revision of the code, as well as
>> `slotting' the packages themselves), determining elf-version, ld
>> modifications, as well as a few other things. It's been implemented at
>> my work [Ironport] from what I've been told, but 1) I'm not sure how
>> complete it is, 2) I'm not sure how tested it is, and 3) it hasn't
>> been reviewed yet and I'm not sure how much would be put back in the
>> community at large to be honest...
>
> Or you can take the vendor's approach and make a static binary with all t=
he
> dependencies (i.e., libraries) compiled in.
Yes, but that would require some thinking ahead and willingness to
distribute bloated binaries ;)... some relationships have been burned
because of acquisitions and the former vendor and licensing agreements
don't permit some folks to work with others due to bad blood :\...
Cheers,
-Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7d6fde3d1002151701w5b7720few70e474e82458f8bf>