Re: shared libs and ports, maybe a proposal

2010-07-09 Thread Marc Espie
On Thu, Jul 08, 2010 at 08:22:38PM +, Christian Weisgerber wrote: I think both sthen@ and I have mentioned before that we really like how FreeBSD has the revision in a separate PORTREVISION variable that is much easier and less error prone to increment than pX suffixes in PKGNAME.

Re: shared libs and ports, maybe a proposal

2010-07-09 Thread Landry Breuil
On Fri, Jul 9, 2010 at 10:16 AM, Marc Espie es...@nerim.net wrote: On Thu, Jul 08, 2010 at 08:22:38PM +, Christian Weisgerber wrote: I think both sthen@ and I have mentioned before that we really like how FreeBSD has the revision in a separate PORTREVISION variable that is much easier and

Re: shared libs and ports, maybe a proposal

2010-07-09 Thread Marc Espie
I remember why I did not do it before... there is a technical. The way we build FULLPKGNAMEs with the interaction with flavors makes this rather awkward. Anyways, my make-fu did improve markedly since last time I tried, so this ought to do the trick. If you get a headache while reading this,

shared libs and ports, maybe a proposal

2010-07-08 Thread Marc Espie
each time xenocara farts, we get new libs (or less libs). in order for updates to work, we *should* propagate those changes to @wantlib in each port. This currently isn't done automatically... check-lib-depends is sloooww (needs to check every file before packaging) and not even flawless. I'm

Re: shared libs and ports, maybe a proposal

2010-07-08 Thread Marc Espie
On Thu, Jul 08, 2010 at 12:03:47PM +0100, Stuart Henderson wrote: On 2010/07/08 11:50, Marc Espie wrote: each time xenocara farts, we get new libs (or less libs). in order for updates to work, we *should* propagate those changes to @wantlib in each port. This currently isn't done

Re: shared libs and ports, maybe a proposal

2010-07-08 Thread Matthieu Herrb
On Thu, Jul 08, 2010 at 11:50:39AM +0200, Marc Espie wrote: each time xenocara farts, we get new libs (or less libs). in order for updates to work, we *should* propagate those changes to @wantlib in each port. For the base and xenocara libs, wouldn't it make sense to have some modules

Re: shared libs and ports, maybe a proposal

2010-07-08 Thread Sebastian Reitenbach
On Thursday 08 July 2010 02:03:41 pm Matthieu Herrb wrote: On Thu, Jul 08, 2010 at 11:50:39AM +0200, Marc Espie wrote: each time xenocara farts, we get new libs (or less libs). in order for updates to work, we *should* propagate those changes to @wantlib in each port. For the base and

Re: shared libs and ports, maybe a proposal

2010-07-08 Thread Sam Smith
On Thu, 8 Jul 2010, Marc Espie wrote: On Thu, Jul 08, 2010 at 02:03:41PM +0200, Matthieu Herrb wrote: On Thu, Jul 08, 2010 at 11:50:39AM +0200, Marc Espie wrote: each time xenocara farts, we get new libs (or less libs). in order for updates to work, we *should* propagate those changes to

Re: shared libs and ports, maybe a proposal

2010-07-08 Thread Christian Weisgerber
Marc Espie es...@nerim.net wrote: Briefly, the only info that changes is - p* numbers (e.g., PKGNAME = somethingpN) - WANTLIB for the affected package. As much as I don't like adding, as naddy would put it, more magic, I think the p* numbers could live in a separate file, along with most