jdd wrote:
Andreas Jaeger wrote:
jdd
writes: [...] * this can be very powerfull, but for the very same reason must be very carefully examined. I wonder if it's not risky to 10.2 (don't do again the libzypp error), we must fine tune the definitions and scenarii before going to the implementation.
That's why I start early and asked directly for feedback ;-). We *now* have enough time to do it and fine tune it...
nice :-)
so let's may be describe the problem differently.
Given we must define a new package grouping system, what kind of categorisation is needed and a what time in the day to day openSUSE work.
First, when will this system used:
a1) first time install a2) update a3) system repair (previous install aborted abnormally-for example AC outage) a4) system cleaning (versus usability) a5) system cleaning (versus space left on disk) a6) test system (frequent install/uninstall - for example install _all_ the web editing system available)
Then, package categorisation.
we have currently at least (given all are rpm):
b1) by great desktop system b1-1) kde b1-2) Gnome b1-3) XFCE b1-4) window manager (windowmaker, fvwm...) b1-5) console only
b2) by goal (programming, word processing, multimedia...)
b3) by system size/power b3-1) very low profile computer (up to PII) b3-2) first price computer (new) or old top notch one (from PII to p4, 256Mb ram) b3-3) gamer or top speed computer (p4, more than 1Gb ram...) b3-4) server - may be very strong, probably RAID, VPN, SCSI
jdd
Let me jump in with one fundamental question. The patterns can be arranged in different ways giving almost unlimited freedom to form final result, customized system. The problem is still in the packages that contain binaries. They are compiled with the broadest selection of options, so they can fit in a as many configurations as possible. That gives a lot of unused code and dependencies in custom installation. Having some experience with Gentoo, where all was compiled from scratch I can appreciate fast execution of such binaries. When comes to updates or expansion that requires new compile options, than it is another story. Is it possible to create patterns for special purposes (advanced users) that will combine both approaches, some base that is precompiled and the most used applications and libraries in such system to be customized and then compiled. Basic idea is to allow experienced users to see in advance what functionality they get, how much in code size it will cost, and them make decision what to do. How complicated is to include compilation as one of options in a system creation? How long it may take to document sufficiently compilation options? Is it viable at this point to consider compilation options as dependency control? The last will allow to shrink the system substantially, as user will be able to select functionality, not only package. -- Regards, Rajko. Visit http://en.opensuse.org/MiniSUSE --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory-help@opensuse.org