Mailinglist Archive: opensuse-factory (471 mails)
| < Previous | Next > |
Re: [opensuse-factory] status distribution
- From: Cristian Morales Vega <cmorve69@xxxxxxxx>
- Date: Wed, 17 Jun 2009 14:12:11 +0200
- Message-id: <8235e6f40906170512t76ef9a94vac79d8c85b17c4e6@xxxxxxxxxxxxxx>
2009/6/17 Stephan Kulow <coolo@xxxxxxxxxx>:
If there are a Iot of build fails I would make a full Factory build
with SUSE_ASNEEDED=1 and create an openSUSE:Factory:asneeded project
similar to openSUSE:Factory:Gcc44 with a link to the packages that
failed (with the build log, not sure if that would require an
additional build).
If there is real interest I would expect those packages (or the
library packages they depend on with the real problem) to be fixed for
11.2 release. If so, set SUSE_ASNEEDED=1 again for all post-11.2
Factory builds and we will have all the 11.3 development time to find
and fix the packages that build but with problems... plus any new
build fail, but I don't really expect any package build starting to
fail because of --as-needed between now and 11.2 release.
Meanwhile one could put a ban to SUSE_ASNEEDED=1 for packages that
contain libraries (or allow it only with also
"--no-allow-shlib-undefined") but allow each packager to set
SUSE_ASNEEDED=1 for his packages with only executables if they want
to.
I would really like to have the full distro building with --as-needed,
call it a personal obsession. I had some free time recently and I have
submitted a few patches to fix packages that failed with
--as-needed... a few because they were all I knew. Having a list of
problematic packages would be really helpful.
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
So I would like to hear feedback on this. We have an alternative of course:
leaving binutils as it is and only set SUSE_ASNEEDED=1 in packages where we
expect real benefits. Or we set SUSE_ASNEEDED=0 in all packages creating a
build problem and you guys say we test enough to make as-needed useful.
If there are a Iot of build fails I would make a full Factory build
with SUSE_ASNEEDED=1 and create an openSUSE:Factory:asneeded project
similar to openSUSE:Factory:Gcc44 with a link to the packages that
failed (with the build log, not sure if that would require an
additional build).
If there is real interest I would expect those packages (or the
library packages they depend on with the real problem) to be fixed for
11.2 release. If so, set SUSE_ASNEEDED=1 again for all post-11.2
Factory builds and we will have all the 11.3 development time to find
and fix the packages that build but with problems... plus any new
build fail, but I don't really expect any package build starting to
fail because of --as-needed between now and 11.2 release.
Meanwhile one could put a ban to SUSE_ASNEEDED=1 for packages that
contain libraries (or allow it only with also
"--no-allow-shlib-undefined") but allow each packager to set
SUSE_ASNEEDED=1 for his packages with only executables if they want
to.
I would really like to have the full distro building with --as-needed,
call it a personal obsession. I had some free time recently and I have
submitted a few patches to fix packages that failed with
--as-needed... a few because they were all I knew. Having a list of
problematic packages would be really helpful.
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |