ports and dependency hell
julian at freebsd.org
Wed Feb 8 08:04:09 UTC 2017
On 8/2/17 3:17 am, Grzegorz Junka wrote:
> On 07/02/2017 18:03, Julian Elischer wrote:
>> This is a serious post on a serious issue that ports framework
>> people seem unaware of.
>> The call "It just works under linux, select the versions you want
>> of each package and type make" is often heard around the company.
>> And management is not totally deaf.
> Hi Julian,
> I may not fully understand how it works but what prevents you from
> getting sources for the version you want and typing make in them,
> exactly the way you do it in Linux? It should pick up the versions
> of dependencies currently installed in the system and compile for
> them. Is it only when you want to use the ports infrastructure that
> poses a problem?
Nothing stops me from doing that. It's just that means that the ports
infrastructure is useless and a complete waste of time right?
I'm no ready to admit that, however I may just be in denial.
also, downsides to doing that include:
* not getting any FreeBSD related fixes (many packages don't work well
on FreeBSD without patches)
* not being able to play nice with software installed by packages
* having a hard time installing FreeBSD specific software that is
delivered by ports and pkg as it's primary means of delivery.
* having to manually chase package revisions. In areas where I have no
upsides include the ability to use autotools etc as they are designed
to be used and pkgconf to knit everything together without worring
about version problems. (downside is using autotools :-) )
So there is a price to pay each way..
I'm discouraged to not hear back from any of the ports 'committee'.
> freebsd-ports at freebsd.org mailing list
> To unsubscribe, send any mail to
> "freebsd-ports-unsubscribe at freebsd.org"
More information about the freebsd-ports