Anaconda selects these if we're on an appropriate system, so don't pull them in by default. --- comps-f16.xml.in | 2 -- comps-f17.xml.in | 2 -- 2 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/comps-f16.xml.in b/comps-f16.xml.in index be87539..819a907 100644 --- a/comps-f16.xml.in +++ b/comps-f16.xml.in @@ -756,8 +756,6 @@ <packagereq type="mandatory">util-linux</packagereq> <packagereq type="mandatory">vim-minimal</packagereq> <packagereq type="mandatory">yum</packagereq> - <packagereq type="default">efibootmgr</packagereq> - <packagereq type="default">grub2</packagereq> <packagereq type="default">ppc64-utils</packagereq> <packagereq type="default">s390utils</packagereq> <packagereq type="default">sendmail</packagereq> diff --git a/comps-f17.xml.in b/comps-f17.xml.in index 267fafa..fe3fa63 100644 --- a/comps-f17.xml.in +++ b/comps-f17.xml.in @@ -691,8 +691,6 @@ <packagereq type="mandatory">util-linux</packagereq> <packagereq type="mandatory">vim-minimal</packagereq> <packagereq type="mandatory">yum</packagereq> - <packagereq type="default">efibootmgr</packagereq> - <packagereq type="default">grub2</packagereq> <packagereq type="default">ppc64-utils</packagereq> <packagereq type="default">s390utils</packagereq> <packagereq type="default">sendmail</packagereq>
Peter Jones (pjones@redhat.com) said:
Anaconda selects these if we're on an appropriate system, so don't pull them in by default.
Are they required somewhere appropriately that they'll get pulled into a compose if they fall out of comps?
Bill
comps-f16.xml.in | 2 -- comps-f17.xml.in | 2 -- 2 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/comps-f16.xml.in b/comps-f16.xml.in index be87539..819a907 100644 --- a/comps-f16.xml.in +++ b/comps-f16.xml.in @@ -756,8 +756,6 @@ <packagereq type="mandatory">util-linux</packagereq> <packagereq type="mandatory">vim-minimal</packagereq> <packagereq type="mandatory">yum</packagereq>
<packagereq type="default">efibootmgr</packagereq><packagereq type="default">grub2</packagereq> <packagereq type="default">ppc64-utils</packagereq> <packagereq type="default">s390utils</packagereq> <packagereq type="default">sendmail</packagereq>diff --git a/comps-f17.xml.in b/comps-f17.xml.in index 267fafa..fe3fa63 100644 --- a/comps-f17.xml.in +++ b/comps-f17.xml.in @@ -691,8 +691,6 @@ <packagereq type="mandatory">util-linux</packagereq> <packagereq type="mandatory">vim-minimal</packagereq> <packagereq type="mandatory">yum</packagereq>
<packagereq type="default">efibootmgr</packagereq><packagereq type="default">grub2</packagereq> <packagereq type="default">ppc64-utils</packagereq> <packagereq type="default">s390utils</packagereq> <packagereq type="default">sendmail</packagereq>-- 1.7.6
Bill Nottingham (notting@redhat.com) said:
Peter Jones (pjones@redhat.com) said:
Anaconda selects these if we're on an appropriate system, so don't pull them in by default.
Are they required somewhere appropriately that they'll get pulled into a compose if they fall out of comps?
... appears not. So, we'd need some other way to ensure they get on the DVD. We could add them to the kickstart file as an exception, although that may not translate well to all downstream distributions. We could move all the bootloaders to a group that kickstarts and downstreams need, but isn't exposted to the user.
Bill
On 09/29/2011 02:03 PM, Bill Nottingham wrote:
Peter Jones (pjones@redhat.com) said:
Anaconda selects these if we're on an appropriate system, so don't pull them in by default.
Are they required somewhere appropriately that they'll get pulled into a compose if they fall out of comps?
Hrm. Probably not. Should I leave them in but put the type as something other than default, instead of this?
Bill
comps-f16.xml.in | 2 -- comps-f17.xml.in | 2 -- 2 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/comps-f16.xml.in b/comps-f16.xml.in index be87539..819a907 100644 --- a/comps-f16.xml.in +++ b/comps-f16.xml.in @@ -756,8 +756,6 @@ <packagereq type="mandatory">util-linux</packagereq> <packagereq type="mandatory">vim-minimal</packagereq> <packagereq type="mandatory">yum</packagereq> -<packagereq type="default">efibootmgr</packagereq> -<packagereq type="default">grub2</packagereq> <packagereq type="default">ppc64-utils</packagereq> <packagereq type="default">s390utils</packagereq> <packagereq type="default">sendmail</packagereq> diff --git a/comps-f17.xml.in b/comps-f17.xml.in index 267fafa..fe3fa63 100644 --- a/comps-f17.xml.in +++ b/comps-f17.xml.in @@ -691,8 +691,6 @@ <packagereq type="mandatory">util-linux</packagereq> <packagereq type="mandatory">vim-minimal</packagereq> <packagereq type="mandatory">yum</packagereq> -<packagereq type="default">efibootmgr</packagereq> -<packagereq type="default">grub2</packagereq> <packagereq type="default">ppc64-utils</packagereq> <packagereq type="default">s390utils</packagereq> <packagereq type="default">sendmail</packagereq> -- 1.7.6
Peter Jones (pjones@redhat.com) said:
On 09/29/2011 02:03 PM, Bill Nottingham wrote:
Peter Jones (pjones@redhat.com) said:
Anaconda selects these if we're on an appropriate system, so don't pull them in by default.
Are they required somewhere appropriately that they'll get pulled into a compose if they fall out of comps?
Hrm. Probably not. Should I leave them in but put the type as something other than default, instead of this?
Optional packages aren't pulled into the compose.
Bill
anaconda-devel@lists.fedoraproject.org