Summary: | app-text/ghostscript-gpl: elog messages about bindist should only be shown when I have bindist set | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pacho Ramos <pacho> |
Component: | Current packages | Assignee: | Printing Team <printing> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | qa |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Pacho Ramos
![]() The purpose of the change done in bug 541412 (and previously discussed in http://thread.gmane.org/gmane.linux.gentoo.devel/95123) was to get rid of the bindist flag in ebuilds where it was redundant, and to replace it with RESTRICT="foo? ( bindist )" in these cases (i.e. "djvu? ( bindist )" here). I don't have a strong opinion about the message in pkg_setup(). On the one hand, nothing prevents users (technically) from distributing binpkgs built with any combination of USE flags, so the warning still serves a purpose. On the other hand, it is somewhat redundant with RESTRICT="bindist", and we have many packages that have a restriction only but don't output any warning in addition. In any case, Portage users can set ACCEPT_RESTRICT="* -bindist" in their make.conf to prevent building of packages that cannot be binary redistributed. (In reply to Ulrich Müller from comment #1) > On > the other hand, it is somewhat redundant with RESTRICT="bindist", and we > have many packages that have a restriction only but don't output any warning > in addition. > Removed in 9.20 |