[gentoo-dev] Re: [RFC] Add operator + for licenses (EAPI-4 ?)
Sebastian Pipping posted on Tue, 01 Sep 2009 04:21:49 +0200 as excerpted: However I do notice that GPL-2+ could make things easier. Why not introduce a license group for it like @GPL-2+ or so, instead? That would be transparent and use existing means. I've always thought Gentoo needed plus versions of the versioned licenses, anyway. GPL-2, GPL-2+, GPL-3, and GPL-3+, should all be different licenses, because really, they are. Then again, there's the various waiver conditions, which I /do/ see are covered with separate licenses for many of them, already. But someone already mentioned a license audit, which in practical terms would be needed to really depend on the LICENSE variable in any case. -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman
[gentoo-dev] Re: [gentoo-dev-announce] Qt3 deprecation
Qt3 deprecation is now tracked in bug #283429 [1] Regards, jer [1] https://bugs.gentoo.org/283429
Re: [gentoo-portage-dev] ebuild --debug takes forever when FEATURES contains keeptemp: detects QA warnings in build.log
Amit Dor-Shifer wrote: Hi. When I'm executing ebuild --debug /path/to/my/ebuild.ebuild /some/file, ebuild keeps dumping QA warnings to /some/file. I think its because its grepping for : warning : in build.log, and such messages are quoted into build.log because of the use of --debug. Maybe we just need to disable that QA check when --debug is enabled. What specific QA warnings are you getting? -- Thanks, Zac
Re: [gentoo-portage-dev] ebuild --debug takes forever when FEATURES contains keeptemp: detects QA warnings in build.log
I think it's not that I'm getting any specific warning, but rather that
the warnings get quoted in build.log in debug mode:
amit0 ~ $ cat
/usr/portage/local/myebuilds/test/test-mkdir/test-mkdir-1.0.ebuild
SRC_URI=
KEYWORDS=amd64
# Make sure you have the SLOT variable in the ebuild. If you don't plan
to use it, don't remove it. Put in SLOT=0.
SLOT=0
# You must (according to the Gentoo ebuild HOWTO) include the IUSE
variable even if there are no USE flags in use.
IUSE=
DEPEND=
RDEPEND=${DEPEND}
src_install()
{
diropts -m0777
dodir /tmp/test-mkdir
}
amit0 ~ $ rm -fr /var/tmp/portage/test/test-mkdir-1.0/temp/
amit0 ~ $ time (ebuild --debug
/usr/portage/local/myebuilds/test/test-mkdir/test-mkdir-1.0.ebuild
/tmp/bla install)
real0m3.456s
user0m2.527s
sys 0m1.002s
amit0 ~ $ grep -qs ': warning:'
/var/tmp/portage/test/test-mkdir-1.0/temp/build.log
amit0 ~ $ echo $?
0
amit0 ~ $ grep -m 3 ': warning:'
/var/tmp/portage/test/test-mkdir-1.0/temp/build.log
+ msgs=(: warning: dereferencing type-punned pointer will break
strict-aliasing rules$ : warning: implicit declaration of function
: warning: incompatible implicit declaration of built-in function :
warning: is used uninitialized in this function$ : warning:
comparisons like X=Y=Z do not have their mathematical meaning$ :
warning: null argument where non-null required )
+ [[ -n : warning: dereferencing type-punned pointer will break
strict-aliasing rules$ ]]
+ m=': warning: dereferencing type-punned pointer will break
strict-aliasing rules$'
amit0 ~ $ time (ebuild --debug
/usr/portage/local/myebuilds/test/test-mkdir/test-mkdir-1.0.ebuild
/tmp/bla install)
# preemting ebuild after a ~30 sec. hang
^C^C
real0m31.257s
user0m22.578s
sys 0m8.949s
Amit
Zac Medico wrote:
Amit Dor-Shifer wrote:
Hi.
When I'm executing ebuild --debug /path/to/my/ebuild.ebuild
/some/file, ebuild keeps dumping QA warnings to /some/file. I think its
because its grepping for : warning : in build.log, and such messages
are quoted into build.log because of the use of --debug.
Maybe we just need to disable that QA check when --debug is enabled.
What specific QA warnings are you getting?
