On Sun, May 10, 2009 at 12:25:17AM +0900, Izumi Tsutsui wrote: > Quentin Garnier wrote: > > > I definitely agree with Andrew that there is no need to overthink the > > name of the set. While "modules.tgz" might not reflect the exact > > reality, it is well know what it is about, and I don't think there'd be > > any confusion about it. > > Well, it would be really painful to change the set name > (too many files to be fixed, including sysinst per ports), > so I'd like to confirm there is no strong objection :-) I understand your concern. My feeling is that modules.tgz will never be right, but always close enough to the reality. > Current other sets (base, comp, text...) are somewhat meaningful > even for users who don't know NetBSD internals (though some of > them are not so clear), so I wonder if the kernel module set should > have the similar naming scheme. I think it's use that got them meaning, except maybe for games.tgz. I don't worry too much about that. [...] > > - add an option to build.sh's sets and install targets to only install > > the sets listed, so you'd use e.g. ./build.sh -s modules install=/. > > How about "build.sh install_module=/dir" as darcy@ suggest > on current-users? Well, my point was that it'd be useful for other stuff to be able to install only a selection of sets through build.sh, but I won't fight it, if someone implements what darcy@ suggests, I'll just be glad :-) -- Quentin Garnier - cube%cubidou.net@localhost - cube%NetBSD.org@localhost "See the look on my face from staying too long in one place [...] every time the morning breaks I know I'm closer to falling" KT Tunstall, Saving My Face, Drastic Fantastic, 2007.
Attachment:
pgpzaSUjSyEO7.pgp
Description: PGP signature