Mailinglist Archive: opensuse-factory (471 mails)
| < Previous | Next > |
Re: [opensuse-factory] status distribution
- From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
- Date: Sat, 20 Jun 2009 03:01:37 -0500
- Message-id: <200906200301.38150.drankinatty@xxxxxxxxxxxxxxxxxx>
On Wednesday 17 June 2009 07:27:03 am Stephan Kulow wrote:
Not that I have a lot of input on build intricacies, but I whole
heartedly
agree with Stephan here. Time needs to be allowed for the development of 11.2
to "Settle" in the short amount of time between now and release so a clean up
of the bugs in the packages can take place without introducing new ones with
asneeded.
Regardless of how much manpower is dedicated to
rushing-pushing-tinkering and
changing every package to build with asneeded between now and 11.2 release,
reality says you will be chasing asneeded bugs all the way up to the release
date and then bandaiding packages at the last minute to press DVD's and
inevitably then many unintended consequences of the asneeded rush won't show
up until after the DVD's are pressed because the state of build process wasn't
frozen (asneeded=0/asneeded=1) long enough before release to allow adequate
testing to minimize the number of "Oopses" in the final product.
If adequate time isn't allowed for simply ironing out the packages with
their
current build procedure, I think you are just setting yourselves up for
failure and being caught short on time to get it all done. Personally, I would
like to see 11.2 be a clean release without 1.2G of package updates within the
first 30 days of release needed to fix problems that would have been avoided
if a smarter and more conservative approach to getting 11.2 DVD ready had been
taken.
There is only so much that can be done. The decision to freeze/decide
upon
the build process for packages seems like something that needs to happen
yesterday so the cleanup can begin.
Just my .02 that applies to any large undertaking whether writing code
or
changing APU turbine speed sensors on the shuttle. (there are 3 per turbine if
you are interested)(Manufactured by Sunstrand)
--
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
Am Mittwoch 17 Juni 2009 schrieb Cristian Morales Vega:
2009/6/17 Stephan Kulow <coolo@xxxxxxxxxx>:
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.
My current plan is to put SUSE_ASNEEDED=0 in all packages failing atm
and then leave it to the packagers to take out and fix on their own
schedule.
http://www.suse.de/~coolo/asneeded has the logs I greped out - as soon as
suse.de syncs again. Be patient in the next minutes :)
Greetings, Stephan
Not that I have a lot of input on build intricacies, but I whole
heartedly
agree with Stephan here. Time needs to be allowed for the development of 11.2
to "Settle" in the short amount of time between now and release so a clean up
of the bugs in the packages can take place without introducing new ones with
asneeded.
Regardless of how much manpower is dedicated to
rushing-pushing-tinkering and
changing every package to build with asneeded between now and 11.2 release,
reality says you will be chasing asneeded bugs all the way up to the release
date and then bandaiding packages at the last minute to press DVD's and
inevitably then many unintended consequences of the asneeded rush won't show
up until after the DVD's are pressed because the state of build process wasn't
frozen (asneeded=0/asneeded=1) long enough before release to allow adequate
testing to minimize the number of "Oopses" in the final product.
If adequate time isn't allowed for simply ironing out the packages with
their
current build procedure, I think you are just setting yourselves up for
failure and being caught short on time to get it all done. Personally, I would
like to see 11.2 be a clean release without 1.2G of package updates within the
first 30 days of release needed to fix problems that would have been avoided
if a smarter and more conservative approach to getting 11.2 DVD ready had been
taken.
There is only so much that can be done. The decision to freeze/decide
upon
the build process for packages seems like something that needs to happen
yesterday so the cleanup can begin.
Just my .02 that applies to any large undertaking whether writing code
or
changing APU turbine speed sensors on the shuttle. (there are 3 per turbine if
you are interested)(Manufactured by Sunstrand)
--
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |