Re: Remove PFRAG bits in the faq
On Tue, 22 Mar 2016 20:50:26 +0100, Jeremie Courreges-Anglaswrote: > > -Constructs of the form %%flavor%% will trigger the > > inclusion of -PFRAG.flavor. > > That part is still accurate. Yes, I didn't understand PFRAG things that well, thanks for pointing them out :)
Re: Remove PFRAG bits in the faq
Daniel Jakotswrites: > Hi, Bijour, > While looking for something else, I saw that PFRAG bits wasn't removed > from the guide/faq yet. > > Cheers, > Daniel > > Index: differences.html > === > RCS file: /cvs/www/faq/ports/differences.html,v > retrieving revision 1.18 > diff -u -p -r1.18 differences.html > --- differences.html 22 Mar 2016 10:56:56 - 1.18 > +++ differences.html 22 Mar 2016 19:35:01 - > @@ -417,10 +417,6 @@ make sense for that port (e.g., FLAV > The WRKDIR is tweaked so that distinct flavors can be built > concurrently without colliding. > > -Constructs of the form %%flavor%% will trigger the inclusion of > -PFRAG.flavor. That part is still accurate. > The %%SHARED%% construct triggers the inclusion > -of PFRAG.shared. > - > bsd.port.subdir.mk understands the extension > SUBDIR=directory,opt1,opt2 to say `build port in directory > with FLAVOR=opt1 opt2.' > Index: guide.html > === > RCS file: /cvs/www/faq/ports/guide.html,v > retrieving revision 1.49 > diff -u -p -r1.49 guide.html > --- guide.html22 Mar 2016 11:01:15 - 1.49 > +++ guide.html22 Mar 2016 19:35:22 - > @@ -531,22 +531,6 @@ Anything not installed can be added to a > Note that PLIST annotations are documented in the > http://man.openbsd.org/?sektion=1query=pkg_create; > >pkg_create(1) manual. > - > -Ports that install shared libraries may have another file called > -PFRAG.shared. > - > -PLIST describes the files being independent of whether the > architecture > -supports shared libraries or not. > - > -PFRAG.shared describes only the files being additionally installed > on > -those architectures that support shared libraries. > - > -PFRAG.noshared describes only the files being additionally > installed on > -architectures that do not support shared libraries. > - > -If a port will only work on an architecture supporting shared > -libraries, for example if it relies on loading modules at runtime with > -dlopen(), set SHARED_ONLY=yes. > > > It is possible some directories do not need to be in the PLIST > Index: testing.html > === > RCS file: /cvs/www/faq/ports/testing.html,v > retrieving revision 1.27 > diff -u -p -r1.27 testing.html > --- testing.html 22 Mar 2016 10:56:56 - 1.27 > +++ testing.html 22 Mar 2016 19:35:34 - > @@ -207,8 +207,7 @@ $ for ms in $(make show=MASTER_SITES) > >package > > - Package creation can break if pkg/PLIST* and/or > - pkg/PFRAG* are wrong. Same here. > + Package creation can break if pkg/PLIST* is wrong. > > >install > -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Remove PFRAG bits in the faq
Hi, While looking for something else, I saw that PFRAG bits wasn't removed from the guide/faq yet. Cheers, Daniel Index: differences.html === RCS file: /cvs/www/faq/ports/differences.html,v retrieving revision 1.18 diff -u -p -r1.18 differences.html --- differences.html22 Mar 2016 10:56:56 - 1.18 +++ differences.html22 Mar 2016 19:35:01 - @@ -417,10 +417,6 @@ make sense for that port (e.g., FLAV The WRKDIR is tweaked so that distinct flavors can be built concurrently without colliding. -Constructs of the form %%flavor%% will trigger the inclusion of -PFRAG.flavor. The %%SHARED%% construct triggers the inclusion -of PFRAG.shared. - bsd.port.subdir.mk understands the extension SUBDIR=directory,opt1,opt2 to say `build port in directory with FLAVOR=opt1 opt2.' Index: guide.html === RCS file: /cvs/www/faq/ports/guide.html,v retrieving revision 1.49 diff -u -p -r1.49 guide.html --- guide.html 22 Mar 2016 11:01:15 - 1.49 +++ guide.html 22 Mar 2016 19:35:22 - @@ -531,22 +531,6 @@ Anything not installed can be added to a Note that PLIST annotations are documented in the http://man.openbsd.org/?sektion=1query=pkg_create; >pkg_create(1) manual. - -Ports that install shared libraries may have another file called -PFRAG.shared. - -PLIST describes the files being independent of whether the architecture -supports shared libraries or not. - -PFRAG.shared describes only the files being additionally installed on -those architectures that support shared libraries. - -PFRAG.noshared describes only the files being additionally installed on -architectures that do not support shared libraries. - -If a port will only work on an architecture supporting shared -libraries, for example if it relies on loading modules at runtime with -dlopen(), set SHARED_ONLY=yes. It is possible some directories do not need to be in the PLIST Index: testing.html === RCS file: /cvs/www/faq/ports/testing.html,v retrieving revision 1.27 diff -u -p -r1.27 testing.html --- testing.html22 Mar 2016 10:56:56 - 1.27 +++ testing.html22 Mar 2016 19:35:34 - @@ -207,8 +207,7 @@ $ for ms in $(make show=MASTER_SITES) package - Package creation can break if pkg/PLIST* and/or - pkg/PFRAG* are wrong. + Package creation can break if pkg/PLIST* is wrong. install