[opensuse-packaging] 2nd reminder to fix your packages for compiling with GCC 4.3
[BCCed to devel, labs as not all people seem to be subscribed to opensuse-packagers] Hi, this is a reminder for you to have a look at your packages that fail in the BETA distribution (which has GCC 4.3 as its compiler). If you think that the compiler is at fault feel free to report these issues back to me or file a bugzilla for them. Builds with a slightly newer version of GCC for x86_64 and i586 are also available in the home:rguenther:playground build service project. Thanks, Richard. -- Richard Guenther <rguenther@suse.de> Novell / SUSE Labs SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746 - GF: Markus Rex --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 2007-10-22 15:08:07 +0200, Richard Guenther wrote:
[BCCed to devel, labs as not all people seem to be subscribed to opensuse-packagers]
still? i should bother henne. ;)
this is a reminder for you to have a look at your packages that fail in the BETA distribution (which has GCC 4.3 as its compiler). If you think that the compiler is at fault feel free to report these issues back to me or file a bugzilla for them.
Builds with a slightly newer version of GCC for x86_64 and i586 are also available in the home:rguenther:playground build service project.
just a reminder: we have the rule that a readme.suse or suse.tar.bz2 should be prefixed with the package name to avoid collisions when installing the src rpm. that said it is not the smartest idea that many people call their patches "gcc-4.3.diff". please prefix your patches atleast with the package name. libakode-2.0.2_gcc-4.3.diff is better and people later know when the patch was touched the last time. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Hi, On Mon, 22 Oct 2007, Marcus Rueckert wrote:
we have the rule that a readme.suse or suse.tar.bz2 should be prefixed with the package name to avoid collisions when installing the src rpm.
We should fix the reason for this stupid rule, namely that installing a source rpm places all files in the same directory. That's just insane. Ciao, Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Monday 22 October 2007 17:31, Michael Matz wrote:
Hi,
On Mon, 22 Oct 2007, Marcus Rueckert wrote:
we have the rule that a readme.suse or suse.tar.bz2 should be prefixed with the package name to avoid collisions when installing the src rpm.
We should fix the reason for this stupid rule, namely that installing a source rpm places all files in the same directory. That's just insane.
I fully agree. The most sane approach IMHO would be to expand the sources and specfile into the current directory; there is no such thing as "installing" a source rpm anyway, the files only get extracted somewhere. Redefining _sourcedir and _specdir alone gets rid of this stupidity, by the way: rpm --eval '%define _sourcedir %(pwd)' \ --eval '%define _specdir %_sourcedir' \ -i ... In fact there is just as little reason for _rpmdir and _srcrpmdir being absolute paths. I have been using the attached script for sanely building a package on the local machine, e.g., xrpm --rebuild foo.src.rpm xrpm -ba foo.spec This works like a charm... Thanks, Andreas
On Monday 22 October 2007, Marcus Rueckert wrote:
we have the rule that a readme.suse or suse.tar.bz2 should be prefixed with the package name to avoid collisions when installing the src rpm.
that said it is not the smartest idea that many people call their patches "gcc-4.3.diff". please prefix your patches atleast with the package name.
I think this rule should either be dropped or enforced. I disagree about the usefulness of this rule in general. Greetings, Dirk -- RPMLINT information under http://en.opensuse.org/Packaging/RpmLint --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 2007-10-23 11:25:08 +0200, Dirk Mueller wrote:
On Monday 22 October 2007, Marcus Rueckert wrote:
we have the rule that a readme.suse or suse.tar.bz2 should be prefixed with the package name to avoid collisions when installing the src rpm.
that said it is not the smartest idea that many people call their patches "gcc-4.3.diff". please prefix your patches atleast with the package name.
I think this rule should either be dropped or enforced. I disagree about the usefulness of this rule in general.
so it is not useful to install multiple src rpms conflict free at the same time? besides it worked well for other files aswell in the past. about the enforcement part: i only see one way to enforce it and that would mean a naming pattern for files inside a package. there was already a proposal about that but i havent seen any agreement on that either. many people use different naming patterns. most people use the package name in the filename. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Marcus Rueckert wrote:
On 2007-10-23 11:25:08 +0200, Dirk Mueller wrote:
On Monday 22 October 2007, Marcus Rueckert wrote:
we have the rule that a readme.suse or suse.tar.bz2 should be prefixed with the package name to avoid collisions when installing the src rpm.
that said it is not the smartest idea that many people call their patches "gcc-4.3.diff". please prefix your patches atleast with the package name. I think this rule should either be dropped or enforced. I disagree about the usefulness of this rule in general.
so it is not useful to install multiple src rpms conflict free at the same time?
That's much easier to achieve with a reasonable rpm config. Eg. echo "%_topdir $HOME/packages" >>~/.rpmmacros echo "%_sourcedir %_topdir/SOURCES/%name" >>~/.rpmmacros mkdir ~/packages/{SPECS,SOURCES,RPMS,SRPMS} would be a good starting point. Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Le mardi 23 octobre 2007, Michal Marek a écrit :
Marcus Rueckert wrote:
so it is not useful to install multiple src rpms conflict free at the same time?
That's much easier to achieve with a reasonable rpm config. Eg. echo "%_topdir $HOME/packages" >>~/.rpmmacros echo "%_sourcedir %_topdir/SOURCES/%name" >>~/.rpmmacros mkdir ~/packages/{SPECS,SOURCES,RPMS,SRPMS} would be a good starting point.
Can't such macros be defined or overwritten system-wide? Having %_sourcedir set to /usr/src/packages/SOURCES/%name (instead of the current default /usr/src/packages/SOURCES) would already a very nice improvement. Thanks, -- Jean Delvare Suse L3 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (8)
-
Andreas Gruenbacher -
Dirk Mueller -
Jean Delvare -
Marcus Rueckert -
Marcus Rueckert -
Michael Matz -
Michal Marek -
Richard Guenther