Re: Where do we want PKG_ARCH in Makefile?

2016-03-25 Thread Giannis Tsaraias
On Mon, Mar 21, 2016 at 07:09:52PM +, Nigel Taylor wrote: > > Should portgen be updated? > > Perl ports should have normally a PKG_ARCH = * added to the Makefile. > When perl uses C or other languages PKG_ARCH = * should not be present, > a WANTLIB += perl should. > > To find which either rea

Re: Where do we want PKG_ARCH in Makefile?

2016-03-23 Thread Nigel Taylor
On 03/22/16 13:45, Stuart Henderson wrote: >> $ portcheck >> www/p5-HTML-Base >> >> portcheck fails to find this one... It could find problem by analysing >> the PLIST > >> I do have a fixed version of p5-HTML-Base. Replace ${P5ARCH} by >> ${P5SITE} in the do-install:, recreate pkg/PLIST, and bum

Re: Where do we want PKG_ARCH in Makefile?

2016-03-22 Thread Stuart Henderson
We are going to have to be careful with these perl WANTLIBs, now that SHARED_ONLY isn't used they are easy to miss, and worse some people may try to remove them because they say "extra", which will mess things up for future perl updates. This might be a useful addition to portcheck. On 2016/03/21

Re: Where do we want PKG_ARCH in Makefile?

2016-03-21 Thread Nigel Taylor
On 03/20/16 10:33, Stuart Henderson wrote: > Watch out for p5-libintl, it currently does not have SHARED_ONLY=Yes > and should do. Not touching it myself now to avoid getting in your way. > > These also are wrong, and have been for some time. $ pwd /usr/ports/packages/amd64/no-arch $ pkg_info -

Re: Where do we want PKG_ARCH in Makefile?

2016-03-20 Thread Kirill Bychkov
On Sun, March 20, 2016 12:24, Stuart Henderson wrote: > On 2016/03/20 02:04, Christian Weisgerber wrote: >> The good news is that the end of the SHARED_ONLY removal is in >> sight. >> >> The not so great news is that the final step will involve touching >> about 1600 perl ports. Most of these will

Re: Where do we want PKG_ARCH in Makefile?

2016-03-20 Thread Stuart Henderson
Watch out for p5-libintl, it currently does not have SHARED_ONLY=Yes and should do. Not touching it myself now to avoid getting in your way.

Re: Where do we want PKG_ARCH in Makefile?

2016-03-20 Thread Stuart Henderson
On 2016/03/20 02:04, Christian Weisgerber wrote: > The good news is that the end of the SHARED_ONLY removal is in > sight. > > The not so great news is that the final step will involve touching > about 1600 perl ports. Most of these will gain a PKG_ARCH=* setting. > Any particular wishes where in

Where do we want PKG_ARCH in Makefile?

2016-03-19 Thread Christian Weisgerber
The good news is that the end of the SHARED_ONLY removal is in sight. The not so great news is that the final step will involve touching about 1600 perl ports. Most of these will gain a PKG_ARCH=* setting. Any particular wishes where in the port Makefile PKG_ARCH should go, after which other vari