On Wednesday 12 July 2006 12:25 pm, Andreas Jaeger wrote: > You got it ;-). It's really powerful and you could do such stuff. > > The question is do we want to do it this way? It makes it difficult > to maintain them...
It does introduce an extra step, at least. Whenever you create a package, you have to choose a group. You can think of this as just another kind of group. Also, when you split a package, you are consciously thinking about this grouping. PostgreSQL is obviously a database, and the postgresql-python subpackage is clearly meant for Python. So basically, the best way to maintain this is to do it during package creation time. I'm thinking of the following scenarios: - The groups can be selected when the package is added to the buildservice. You are asked for name, summary, and description already. This is just one or two more pieces of metadata - The groups can be specified as comment-metadata at the top of the spec file - If RPM is modified, new tags could be added, allowing the data to be placed directly in the header. With this, you could easily generate the selection files for an arbitrary collection of RPMs -- James Oakley [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
