* Roman Drahtmueller wrote on Thu, Nov 15, 2001 at 12:34 +0100:
Are you sure? SuSE scripts honor quotas, so I would wonder why...
Well, it worked on my systems, flawlessly... Strange.
There is nothing like the SuSE build farm on this planet, promised. Each single package that we publish, be it on the CDs or in the update tree, is being built in an own mini installation where dependencies between packages are resolved automatically.
That means, the filesystem is in a defined, orgininal state before _each_ package build? Then I wonder why depencies changed in a few packages.
In fact, this system enables us to basically build a 6.4 distribution in about 17 hours, from scratch/source, with all updated packages, and 6 CDs in your hands, at the very same configuration.
Off Topic, but very interesting :) How do you do that? It remebers to "make world" :) I would expect that some configure would use some lib which is not a default or similar. But shouldn't be a problem since RPM is smart :)
kernels do not depend on any library.
Was meant as example for any packet. Kernel depends on modules (insmod i.e.) and on /usr/src/linux/Documentation/Changes: - Binutils 2.8.1.0.23 - Linux libc6 C Library 2.0.7pre6 - Net-tools 1.52 and others. Not only for build, for operation, too.
In fact, they do not depend on anything, the kernel binary rpm can run standalone without anything else (while it may not make sense in most cases). By consequence, you are able to use a 2.4 kernel RPM built on a SuSE-5.3 distribution and install it on a 7.3, and it should work out of the box.
I would expect the first problem when trying to load a network driver or problems with /dev/tty or with ioctrls or with any other things. I have somewhere a server with 5.1 I think, maybe I'll try a 2.4.x kernel :) Just for fun :)
if he don't care about all the dependencies of a system, and also don^'t explain correctly all the consequence on all the end users...
Or Linus? I'm sure he never build no SuSE RPM at all :)
At least he uses SuSE systems, while he doesn't make a fuss about that... Building an rpm is really easy once you found the basics.
I really like RPMs. And I really like that SuSE use it too, in contrast they could decided to make an SPM or so. RPM is not that bad, really.
The SuSE spec files are very clear to read, they all look the same, and in their comments you can find the packages that are required to be installed for the package to build.
Yes, I know, I patched a few packages... The onliest detail: RPMs are not backward-compatible. rpm --rebuild package-7.3.src.rpm won't work out of the box on a 7.1 or so, but this is not an real issue :)
Get some source rpm and do rpm --rebuild source.rpm. Funny things happen. :-)
I already spent some nights on "fixing" SPEC files for various RPMs. I know what you're talking about :) And by this I know that RPM building is a real complex task. And SuSE has soem hunderts to build. Ohh, I'm lucky, I have only a very few :) :) List, I'm sorry for this OT mail but a part of security concepts is to know about the processes of the supplied components as you know... Well, so it's not really OT :) oki, Steffen -- Dieses Schreiben wurde maschinell erstellt, es trägt daher weder Unterschrift noch Siegel.