Re: Installing a different PORTVERSION based on OSVERSION?
On Sun, Feb 14, 2010 at 2:20 PM, Darren Pilgrim wrote: > Garrett Cooper wrote: >> >> Vendor 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 >> This 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 the > 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 ___ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[email protected]"
Re: Installing a different PORTVERSION based on OSVERSION?
Garrett Cooper wrote: Vendor 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 This 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 the dependencies (i.e., libraries) compiled in. ___ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[email protected]"
Re: Installing a different PORTVERSION based on OSVERSION?
On Sun, Feb 14, 2010 at 12:58 PM, Darren Pilgrim wrote:
> Wesley Shields wrote:
>>
>> On Sat, Feb 13, 2010 at 07:26:39PM -0800, Darren Pilgrim wrote:
>>>
>>> I'm working on a revision to a port where the current version doesn't
>>> work on 8.0-R; however, an older version does. Rather than roll the entire
>>> port back to an older version, I'd like to have the newer version available
>>> to 7.x and older and the older version available to 8.x and newer. Is it
>>> appropriate to install different versions of a port based on ${OSVERSION}?
>>> If so, do I just set the necessary variables after including
>>> bsd.port.pre.mk?
>>
>> This seems like a bad idea to me. How much effort would it take to fix
>> the port on 8.x and newer?
>
> The port contains a static-linked binary from the vendor--not something I
> can patch.
>
>> The other option is to mark it broken on 8.x and newer.
>
> The port currently sets BROKEN if OSVERSION >= 80.
Vendor 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
This 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...
HTH,
-Garrett
___
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[email protected]"
Re: Installing a different PORTVERSION based on OSVERSION?
Wesley Shields wrote:
On Sat, Feb 13, 2010 at 07:26:39PM -0800, Darren Pilgrim wrote:
I'm working on a revision to a port where the current version doesn't
work on 8.0-R; however, an older version does. Rather than roll the
entire port back to an older version, I'd like to have the newer version
available to 7.x and older and the older version available to 8.x and
newer. Is it appropriate to install different versions of a port based
on ${OSVERSION}? If so, do I just set the necessary variables after
including bsd.port.pre.mk?
This seems like a bad idea to me. How much effort would it take to fix
the port on 8.x and newer?
The port contains a static-linked binary from the vendor--not something
I can patch.
The other option is to mark it broken on 8.x and newer.
The port currently sets BROKEN if OSVERSION >= 80.
___
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[email protected]"
Re: Installing a different PORTVERSION based on OSVERSION?
On Sat, Feb 13, 2010 at 07:26:39PM -0800, Darren Pilgrim wrote:
> I'm working on a revision to a port where the current version doesn't
> work on 8.0-R; however, an older version does. Rather than roll the
> entire port back to an older version, I'd like to have the newer version
> available to 7.x and older and the older version available to 8.x and
> newer. Is it appropriate to install different versions of a port based
> on ${OSVERSION}? If so, do I just set the necessary variables after
> including bsd.port.pre.mk?
This seems like a bad idea to me. How much effort would it take to fix
the port on 8.x and newer? The other option is to mark it broken on 8.x
and newer.
-- WXS
___
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[email protected]"
Installing a different PORTVERSION based on OSVERSION?
I'm working on a revision to a port where the current version doesn't
work on 8.0-R; however, an older version does. Rather than roll the
entire port back to an older version, I'd like to have the newer version
available to 7.x and older and the older version available to 8.x and
newer. Is it appropriate to install different versions of a port based
on ${OSVERSION}? If so, do I just set the necessary variables after
including bsd.port.pre.mk?
___
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[email protected]"
