Perl development group in comps again! In case you check available groups in yum, then you can see there is no problem in adding another one.
As was mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=508194 some of our users might find this group useful. I suppose Chris Weyl has good ideas which packages should be included. If there is no simple choice which packages should go into this group, then we can create a wiki page and make a list according to users choice, cpan downloads or whatever.
Marcela Maslanova wrote:
Perl development group in comps again! In case you check available groups in yum, then you can see there is no problem in adding another one.
As was mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=508194 some of our users might find this group useful. I suppose Chris Weyl has good ideas which packages should be included.
Am I the only one who considers this do be a dejavu?
Some of you seem to be unable to understand that a) comps.xml groups are simply junk. b) You are projecting you personal use case onto others.
In other words, I have no use for your "padre" and Chris Weyls' Catalyst packages.
Your desire to add them to a general perl-devel comps.xml group is not to me is of _no use_, and renders a perl-devel comps.xml to be nothing but simple-minded bloat.
If there is no simple choice which packages should go into this group, then we can create a wiki page and make a list according to users choice, cpan downloads or whatever.
This is even more stupid.
Ralf
2009/6/29 Marcela Maslanova mmaslano@redhat.com
Perl development group in comps again! In case you check available groups in yum, then you can see there is no problem in adding another one.
As was mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=508194 some of our users might find this group useful. I suppose Chris Weyl has good ideas which packages should be included. If there is no simple choice which packages should go into this group, then we can create a wiki page and make a list according to users choice, cpan downloads or whatever.
I basically just threw a couple of the "general Perl development tools that aren't just another perl-* package" out there... So things like perltidy, vim-perl-support, eclipse-epic, etc, as well as the Task packages: right now just perl-Task-Catalyst, but Task-Kensho, etc, would also be a good fit as they're not so much code as a paradigm. I'm sure the list can be refined, but it should cover the basics (that I'm aware of, at any rate).
-Chris
perl-devel@lists.fedoraproject.org