Re: [SLE] Buildrequires [kitchen sink] in .spec files? (suse93& suse10)
Philipp Thomas wrote:
If you discover something like that, please file a bug report with https://bugzilla.novell.com so that the maintainer of the package can correct it. Philipp
--- I'd have to file bugs on every package. I haven't found one yet that doesn't have needless dependencies. Simple example -- most of the Suse10 packages require something called libcom_err. Not only does this package not exist under SuSE93, but of course they all build fine under 9.3. This package, (libcom_err), BTW, was added as a "new requirement" for suse10 packages. It wasn't just some old package that the other packages used to rely on but no longer or that "coasted" in tot he new system. So far, every source package I've looked at on suse10 lists "libcom_err" as a "prereq", but none of those packages seem to require it to build. I have some systems running at 9.3 that, historically, have taken days to upgrade to a new version. Sometimes problems aren't found until weeks later, so it's far easier to rebuild a suse10 package from source for those systems than to risk going through significant downtime. Does SuSE/Novell really "need" someone to go through all of the packages? It's not rocket science, more than "tedium". Linda
On Thursday 23 March 2006 22:24, Linda Walsh wrote:
Philipp Thomas wrote:
If you discover something like that, please file a bug report with https://bugzilla.novell.com so that the maintainer of the package can correct it. Philipp
--- I'd have to file bugs on every package. I haven't found one yet that doesn't have needless dependencies.
Simple example -- most of the Suse10 packages require something called libcom_err. Not only does this package not exist under SuSE93, but of course they all build fine under 9.3.
This package, (libcom_err), BTW, was added as a "new requirement" for suse10 packages. It wasn't just some old package that the other packages used to rely on but no longer or that "coasted" in tot he new system. So far, every source package I've looked at on suse10 lists "libcom_err" as a "prereq", but none of those packages seem to require it to build.
I have some systems running at 9.3 that, historically, have taken days to upgrade to a new version. Sometimes problems aren't found until weeks later, so it's far easier to rebuild a suse10 package from source for those systems than to risk going through significant downtime.
Does SuSE/Novell really "need" someone to go through all of the packages? It's not rocket science, more than "tedium".
Linda ========= Linda, You might be finding that trying to build a 10.0 src.rpm for a 9.3 system to be the problem. It would be better if you were to find the 9.3 src.rpm or build your own rpm from the sources. Newer versions are going to have different dependencies than older ones, but I guess you didn't know that? The dependencies are there for a reason and I've very seldom run into something from SUSE that was odd in that way. I do, if I'm trying to build for another version or making some odd changes in the spec or sources.
As you put it, it's not rocket science, but does take a bit of learning how things work. regards, Lee
On Thu, 2006-03-23 at 19:24 -0800, Linda Walsh wrote:
Philipp Thomas wrote:
If you discover something like that, please file a bug report with https://bugzilla.novell.com so that the maintainer of the package can correct it. Philipp
--- I'd have to file bugs on every package. I haven't found one yet that doesn't have needless dependencies.
Simple example -- most of the Suse10 packages require something called libcom_err. Not only does this package not exist under SuSE93, but of course they all build fine under 9.3.
This package, (libcom_err), BTW, was added as a "new requirement" for suse10 packages. It wasn't just some old package that the other packages used to rely on but no longer or that "coasted" in tot he new system. So far, every source package I've looked at on suse10 lists "libcom_err" as a "prereq", but none of those packages seem to require it to build.
I have some systems running at 9.3 that, historically, have taken days to upgrade to a new version. Sometimes problems aren't found until weeks later, so it's far easier to rebuild a suse10 package from source for those systems than to risk going through significant downtime.
I see you were never taught to test upgrades on a test system were you before upgrading a production system. Every capable admin knows that.
Does SuSE/Novell really "need" someone to go through all of the packages? It's not rocket science, more than "tedium".
And it's not rocket science to understand packages being used in a more recent version may not work in an older version without being rebuilt on the older version. Libraries may change with a newer version. Do you expect a fender from 2006 Chevy Impala to fit a 2005 model? If all you have to say about SUSE linux is your moaning, groaning, bitching and complaining, that you start using a different distribution. I think you will soon find out that SUSE is one of the best if not the best linux distro available. Keep in mind that if you have a problem with a package included in a SUSE version bitch at the author that actually wrote the package not SUSE that simply included the program in the version distributed. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Friday 24 March 2006 04:24, Linda Walsh wrote:
Simple example -- most of the Suse10 packages require something called libcom_err. Not only does this package not exist under SuSE93, but of course they all build fine under 9.3.
This package, (libcom_err), BTW, was added as a "new requirement" for suse10 packages. It wasn't just some old package that the other packages used to rely on but no longer or that "coasted" in tot he new system. So far, every source package I've looked at on suse10 lists "libcom_err" as a "prereq", but none of those packages seem to require it to build.
If you compile xine without libmpeg-devel installed it will compile just fine. It just won't be able to play mpegs. Most packages that use autotools to build don't have to have everything installed, they will build anyway. They will just be lacking some functionality in the finished binary The fact that it builds isn't proof enough that the necessity wasn't there -- Certified: Yes. Certifiable: of course! jabber ID: anders@rydsbo.net
participants (4)
-
Anders Johansson -
BandiPat -
Ken Schneider -
Linda Walsh