IMHO, the patterns software management feature is far from satisfactory. I tried it out on a recent 10.2 install, and then when I went back and tried to customize my installation (adding and deleting rpms), I ran into strange dependency problems.
For example, I invoked the 'Games' pattern but, wanting to have only a few things such as pyson and ksudoku, I removed the various board and arcade games from the pattern listings. When I hit 'accept', the dependencies put the other stuff back in again. I ended up deleting the 'Games' pattern which, fortunately, allowed the things I didn't want to be deleted and the ones I wanted to be kept. In other situations, deleting a pattern also removed some files I wanted to keep -- and the worst part was that it did not tell me in advance! I have little/no need for the enterprise volume system, but I am not allowed to remove the rpm unless I also delete the 'Base' pattern, in which case I don't know what havoc will be created. The patterns feature ties up things much too tightly, well beyond the actual dependency relationships, and removes choice/freedom from Linux. It is better to use 'groups' if you want control tailored to your needs. The absence of the import/export capability that was in 10.0 is also a major problem. It can take hours (per machine) to manually adjust an installation to one's interests and space limitations, or to do a reinstall of that configuration. A 'critical' bugzilla has been up since 10.1, with no evident action. If the software manager can respond to a mouse for rpm selection, what is so difficult about reading (or writing) an ascii file and changing check marks? -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
