Bug#348609: net-retriever: generic way to limit fetched udebs to certain components?
Package: net-retriever
Version: 1.09
Severity: wishlist
It'd be nice to have a reasonably generic way to say "I only want to get
installer modules from the following archive components" (probably
independently of where packages will be fetched from later).
In Ubuntu I only want bits of netboot installs to be fetched from our
main and restricted components; we demote other unsupported bits to
universe, but occasionally one of them accidentally ends up with
Priority >= standard and gets fetched by netboot installs anyway. I
added a crude hack to avoid this:
diff -Nru /tmp/OUU6ZdtTz0/net-retriever-1.09/net-retriever /tmp/Ff4GunKsJ9/net-retriever-1.09ubuntu1/net-retriever
--- /tmp/OUU6ZdtTz0/net-retriever-1.09/net-retriever 2006-01-04 03:56:50.000000000 +0000
+++ /tmp/Ff4GunKsJ9/net-retriever-1.09ubuntu1/net-retriever 2006-01-17 22:10:04.000000000 +0000
@@ -125,6 +125,12 @@
error "No components listed in $Release."
fi
for comp in $components; do
+ # TODO: Ubuntu-specific hack to avoid pulling in
+ # udebs from unsupported components; is there any
+ # way to make this more generic?
+ if [ "$comp" != main ] && [ "$comp" != restricted ]; then
+ continue
+ fi
for ext in '.gz' ''; do
pkgfile="$comp/debian-installer/binary-$ARCH/Packages$ext"
line=`grep $pkgfile\$ $Release 2>/dev/null`
... but obviously this is pretty crude and I'd like something cleaner.
Perhaps a debconf template with the list of valid components?
--
Colin Watson [cjwatson@debian.org]
Reply to: