On Mon, 2007-06-04 at 10:42 -0400, Robin Norwood wrote: > Jose Pedro Oliveira <jpo@xxxxxxxxxxxx> writes: > > > Robin Norwood wrote: > >> Hi, > >> > >> This patch will remove the Requires that were placed on perl-devel at > >> the end of the f7 cycle. It is proposed for the 'devel' branch (f8). > >> Comments? > > > > If that breaks the assumption that all perl core modules are installed > > by default, I am against (and you already know the reasons). > > Well, how about a compromise - for F7, we added perl-devel to the > package groups in comps.xml so that it was installed by default whenever > perl was installed. This if course meant that these other packages were > pulled in also. When we break the Requires on the other packages, we > could add them to comps.xml alongside perl-devel. This way the default > install would be 'all perl core modules', but one could easily remove > the devel-related bits either at kickstart time (-<packagename> in the > %packages section) or post-install. > > What do you think about this? > > Ralf? Others? Well, I seem to be stumbling from one pit-fall into the next. To me, comps.xml is completely meaningless, because it is not of any relevance to rpm. I.e. if some people think, it's helpful to them, so be it. Wrt. José's point: In a nutshell he says, "he expects a monolytic perl and doesn't want to change his habits" - At this point, any discussion is moot. IMO, it would be best to add a meta-package "e.g. perl-devel" which would pull in all split out modules. Ralf
