Re: [gentoo-dev] RFC: FEATURES=binchecks strip for plain file packages e.g. latex, perl, python

2013-09-21 Thread Michał Górny
Dnia 2013-09-20, o godz. 20:51:46
Paweł Hajdan, Jr. phajdan...@gentoo.org napisał(a):

 On 9/20/13 12:24 PM, Diego Elio Pettenò wrote:
  As Michał said.
 
 Please consider updating the documentation - ebuild(5):
 
  RESTRICT = [strip,mirror,fetch,userpriv]
 This  should  be a space delimited list of portage features to
 restrict.  You may use conditional syntax to vary restrictions as
 seen above in DEPEND.
 binchecks
Disable all QA checks for binaries.  This should ONLY be
used in packages  for which binary checks make no sense
(linux-headers and kernel-sources, for example, can safely
be skipped since they have no binaries).  If the binary
checks need  to  be skipped for other reasons (such as
proprietary binaries), see the QA CONTROL VARIABLES section
for more specific exemptions.
 
 This is currently used at least by sys-apps/man-pages, as well as
 packages in x11-themes and sys-kernel.

This is just another of portage's deviations from the standard. PMS
doesn't list RESTRICT=binchecks, and I suppose this makes using it in
the tree at least a little wrong.

-- 
Best regards,
Michał Górny


signature.asc
Description: PGP signature


[gentoo-dev] RFC: FEATURES=binchecks strip for plain file packages e.g. latex, perl, python

2013-09-20 Thread Justin (jlec)
Hi,

what is your opinion to set

FEATURES=binchecks strip

for all those packages which purely install files. For example python
package only installing scripts, or perl packages or latex. There might
be more.

Justin



signature.asc
Description: OpenPGP digital signature


Re: [gentoo-dev] RFC: FEATURES=binchecks strip for plain file packages e.g. latex, perl, python

2013-09-20 Thread Diego Elio Pettenò
As Michał said.

Diego Elio Pettenò — Flameeyes
flamee...@flameeyes.eu — http://blog.flameeyes.eu/


On Fri, Sep 20, 2013 at 7:52 PM, Michał Górny mgo...@gentoo.org wrote:

 Dnia 2013-09-20, o godz. 19:58:51
 Justin (jlec) j...@gentoo.org napisał(a):

  what is your opinion to set
 
  FEATURES=binchecks strip
 
  for all those packages which purely install files. For example python
  package only installing scripts, or perl packages or latex. There might
  be more.

 Not worth the effort, and definitely not worth the confusion it will
 introduce (why there's FEATURES=strip here? does it install weird
 executables under some circumstances? did it so in the past and someone
 forgot to drop it?).

 In other words, it's awful overuse of RESTRICT for pseudo-optimization.
 RESTRICT is to restrict features when the package can't handle it. It's
 not for skipping no-ops in the name of supposed performance gain.

 If you really want to play like this, show us some benchmarks. Prove
 that it gains anything. Because as far as I can see, this is nowhere
 near a bottleneck for ebuild installs. Unless you can prove it's a real
 gain, a strong 'don't do it' from me.

 --
 Best regards,
 Michał Górny



Re: [gentoo-dev] RFC: FEATURES=binchecks strip for plain file packages e.g. latex, perl, python

2013-09-20 Thread Matt Turner
On Fri, Sep 20, 2013 at 10:58 AM, Justin (jlec) j...@gentoo.org wrote:
 what is your opinion to set

 FEATURES=binchecks strip

 for all those packages which purely install files. For example python
 package only installing scripts, or perl packages or latex. There might
 be more.

It may help to describe what this would improve (presumably reduce the
installation time?).



Re: [gentoo-dev] RFC: FEATURES=binchecks strip for plain file packages e.g. latex, perl, python

2013-09-20 Thread Michał Górny
Dnia 2013-09-20, o godz. 19:58:51
Justin (jlec) j...@gentoo.org napisał(a):

 what is your opinion to set
 
 FEATURES=binchecks strip
 
 for all those packages which purely install files. For example python
 package only installing scripts, or perl packages or latex. There might
 be more.

Not worth the effort, and definitely not worth the confusion it will
introduce (why there's FEATURES=strip here? does it install weird
executables under some circumstances? did it so in the past and someone
forgot to drop it?).

In other words, it's awful overuse of RESTRICT for pseudo-optimization.
RESTRICT is to restrict features when the package can't handle it. It's
not for skipping no-ops in the name of supposed performance gain.

If you really want to play like this, show us some benchmarks. Prove
that it gains anything. Because as far as I can see, this is nowhere
near a bottleneck for ebuild installs. Unless you can prove it's a real
gain, a strong 'don't do it' from me.

-- 
Best regards,
Michał Górny


signature.asc
Description: PGP signature


Re: [gentoo-dev] RFC: FEATURES=binchecks strip for plain file packages e.g. latex, perl, python

2013-09-20 Thread Paweł Hajdan, Jr.
On 9/20/13 12:24 PM, Diego Elio Pettenò wrote:
 As Michał said.

Please consider updating the documentation - ebuild(5):

 RESTRICT = [strip,mirror,fetch,userpriv]
This  should  be a space delimited list of portage features to
restrict.  You may use conditional syntax to vary restrictions as
seen above in DEPEND.
binchecks
   Disable all QA checks for binaries.  This should ONLY be
   used in packages  for which binary checks make no sense
   (linux-headers and kernel-sources, for example, can safely
   be skipped since they have no binaries).  If the binary
   checks need  to  be skipped for other reasons (such as
   proprietary binaries), see the QA CONTROL VARIABLES section
   for more specific exemptions.

This is currently used at least by sys-apps/man-pages, as well as
packages in x11-themes and sys-kernel.

I'm fine either way, let's just make sure our mailing list advice
matches documentation and established practice.

Paweł



signature.asc
Description: OpenPGP digital signature