Re: ports and dependency hell

2017-02-10 Thread Gerard Seibert
On Fri, 10 Feb 2017 00:04:27 +0100, Martin Waschbüsch stated: >Thus, what you describe sounds, imho, like wanting to eat the cake >and have it. What good is a goddamn cake if you cannot eat it? What, should I eat someone else's cake instead? Besides, how could you possibly eat a cake if you did n

Re: ports and dependency hell

2017-02-09 Thread Martin Waschbüsch
> Am 09.02.2017 um 18:14 schrieb Julian Elischer : > > Commercial products are Hardly EVER rolling releases. > they lurch from point of stability to point of stability, with large amounts > of testing between releases. >>> On the pkg side of things we need the ability for pkg to say "yeah I >>>

Re: ports and dependency hell

2017-02-09 Thread Julian Elischer
On 9/2/17 11:02 pm, Steve Wills wrote: Hi Julian, On 02/07/2017 13:03, Julian Elischer wrote: [...] I found this all confusing and vague, but it sounds like what's happening is you need older versions of some software for whatever reason and to provide that you are pulling older versions of port

Re: ports and dependency hell

2017-02-09 Thread Steve Wills
Hi Julian, On 02/07/2017 13:03, Julian Elischer wrote: > This is a serious post on a serious issue that ports framework people > seem unaware of. To be honest, it's kind of a confusing post, at least to me. > It' getting too easy to get into dependency hell here (I've spent the > last week figh

Re: ports and dependency hell

2017-02-08 Thread Grzegorz Junka
On 08/02/2017 08:03, Julian Elischer wrote: 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

Re: ports and dependency hell

2017-02-08 Thread RW via freebsd-ports
On Wed, 8 Feb 2017 16:03:56 +0800 Julian Elischer wrote: > 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

Re: ports and dependency hell

2017-02-08 Thread George Mitchell
On 02/08/17 03:03, Julian Elischer wrote: > [...] > I'm discouraged to not hear back from any of the ports 'committee'. > [...] Possibly because this has been the topic of a number of rancorous mail threads in the last few months already, and everybody is fatigued. What there *hasn't* been is a co

Re: ports and dependency hell

2017-02-08 Thread Kurt Jaeger
Hi! > I'm discouraged to not hear back from any of the ports 'committee'. I'm not from the committee 8-), but I think you raise relevant points. It is not easy to cover them. All of the pkg-developers have their tables full of work, so ... Crafting a well-reflected answer takes time. -- p...@

Re: ports and dependency hell

2017-02-08 Thread Julian Elischer
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 a

Re: ports and dependency hell

2017-02-07 Thread Grzegorz Junka
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

ports and dependency hell

2017-02-07 Thread Julian Elischer
This is a serious post on a serious issue that ports framework people seem unaware of. It' getting too easy to get into dependency hell here (I've spent the last week fighting this) In a production system we have to choose packages from different eras. This is because on an average product