I don't know that it's a hard requirement, but I think every group needs to have at least one default or mandatory package. Otherwise, "yum groupinstall" will have no effect. -- Dennis On Fri, 2010-02-12 at 11:46 -0800, Kevin Wright wrote: > Hi Bill, > > I was wondering if you had a chance to review the patch to comps- > f13.xml.in. > > Thanks, > --Kevin > On Feb 10, 2010, at 7:47 PM, Kevin Wright wrote: > >> >> On Feb 10, 2010, at 10:01 AM, Bill Nottingham wrote: >> >>> Parag N(पराग़) (panemade(a)gmail.com) said: >>>> Forwarding this mail on behalf of Kevin Wright as his mail to >>>> devel >>>> list didn't appeared yet. >>> >>> Seems reasonable. Do you have a patch? >>> >>> Bill >>> -- devel mailing list >>> devel(a)lists.fedoraproject.org >>> https://admin.fedoraproject.org/mailman/listinfo/devel >> >> >> Bill, >> >> I had to re-subscribe to the list. Here's the patch: >> >> cvs diff -u comps-f13.xml.in >> Index: comps-f13.xml.in >> =================================================================== >> RCS file: /cvs/pkgs/comps/comps-f13.xml.in,v >> retrieving revision 1.161 >> diff -u -r1.161 comps-f13.xml.in >> --- comps-f13.xml.in 10 Feb 2010 04:49:19 -0000 1.161 >> +++ comps-f13.xml.in 11 Feb 2010 01:23:33 -0000 >> @@ -1235,6 +1235,44 @@ >> </packagelist> >> </group> >> <group> >> + <id>dogtag</id> >> + <_name>Dogtag Certificate System</_name> >> + <_description>Enterprise-class open source Certificate >> Authority</_description> >> + <default>false</default> >> + <uservisible>true</uservisible> >> + <packagelist> >> + <packagereq type="optional">dogtag-pki-ca-ui</packagereq> >> + <packagereq type="optional">dogtag-pki-common-ui</packagereq> >> + <packagereq type="optional">dogtag-pki-console-ui</ >> packagereq> >> + <packagereq type="optional">dogtag-pki-kra-ui</packagereq> >> + <packagereq type="optional">dogtag-pki-ocsp-ui</packagereq> >> + <packagereq type="optional">dogtag-pki-ra-ui</packagereq> >> + <packagereq type="optional">dogtag-pki-tks-ui</packagereq> >> + <packagereq type="optional">dogtag-pki-tps-ui</packagereq> >> + <packagereq type="optional">osutil</packagereq> >> + <packagereq type="optional">pki-ca</packagereq> >> + <packagereq type="optional">pki-common-javadoc</packagereq> >> + <packagereq type="optional">pki-common</packagereq> >> + <packagereq type="optional">pki-console</packagereq> >> + <packagereq type="optional">pki-java-tools-javadoc</ >> packagereq> >> + <packagereq type="optional">pki-java-tools</packagereq> >> + <packagereq type="optional">pki-kra</packagereq> >> + <packagereq type="optional">pki-native-tools</packagereq> >> + <packagereq type="optional">pki-ocsp</packagereq> >> + <packagereq type="optional">pki-ra</packagereq> >> + <packagereq type="optional">pki-selinux</packagereq> >> + <packagereq type="optional">pki-setup</packagereq> >> + <packagereq type="optional">pki-silent</packagereq> >> + <packagereq type="optional">pki-symkey</packagereq> >> + <packagereq type="optional">pki-tks</packagereq> >> + <packagereq type="optional">pki-tps</packagereq> >> + <packagereq type="optional">pki-util-javadoc</packagereq> >> + <packagereq type="optional">pki-util</packagereq> >> + <packagereq type="optional">tomcatjss</packagereq> >> + </packagelist> >> + </group> >> + <group> >> + <group> >> <id>dns-server</id> >> <_name>DNS Name Server</_name> >> <_description>This package group allows you to run a DNS name >> server (BIND) on the system.</_description> >> >> --Kevin > > -- > devel mailing list > devel(a)lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel

I could have sworn I sent a response already. In any case... Kevin Wright (kwright(a)redhat.com) said: > You may be right. However, if that's the case, then 389 will have > the same problem: In the case of dogtag, it's the only cert server in the group. So it should have default/mandatory set on the proper set of packages so that if you do 'yum groupinstall dogtag', you get a functional cert server. In the directory server case, it's a group that contains all the various directory servers. It's possible someone could choose just to install krb5/ldap. Still, I think it should be adjusted so that groupinstall installs a functional DS. Bill