Re: base-config/00dbootstrap_settings failure
> I guess the correct solution is to make dbootstrap write unstable
> instead of sid, but I don't know how to handle slink and potato.
> Suggestions?
Here is an idea:
slink and sid will never change, their proper names are just that, slink and
sid. Once woody is released someone installing potato will also want that name to not change, it will just stay 'potato'.
If someone is installing 'stable' let us assume that they always want to be
stable, so when stable changes, they want to change as well. Likewise
installing 'testing' people want it to get updated when testing updates.
This patch makes more sense if you know that there is a define WOODY_RELEASED
that handles changing the meanings of the codenames, something like this:
#ifdef WOODY_RELEASED
#define CODENAME_STABLE "woody"
#define CODENAME_TESTING "foo"
#else
#define CODENAME_STABLE "potato"
#define CODENAME_TESTING "woody"
#endif
Index: extract_base.c
===================================================================
RCS file: /cvs/debian-boot/boot-floppies/utilities/dbootstrap/extract_base.c,v
retrieving revision 1.46
diff -u -r1.46 extract_base.c
--- extract_base.c 2001/06/10 21:02:54 1.46
+++ extract_base.c 2001/06/12 21:18:30
@@ -389,9 +389,14 @@
snprintf(prtbuf, sizeof prtbuf, "%d", nf_state.server.port);
write_userconfig("DEBIAN_MIRROR_PORT", prtbuf);
}
-
- write_userconfig ("SUITE", suite);
-
+
+ if (!strcmp(suite, CODENAME_STABLE))
+ write_userconfig ("SUITE", "stable");
+ else if (!strcmp(suite, CODENAME_TESTING))
+ write_userconfig ("SUITE", "testing");
+ else
+ write_userconfig ("SUITE", suite);
+
free (source);
if (NAME_ISREG("/target/etc/inittab",&statbuf)) {
-David
Reply to: