Re: Combining Packages

SJT> Ville is right: don't delete the old dirs. Just cvs rm. Jake> So if we want to do it that way, I don't need any special Jake> support from Norbert. I can just cp the files to the new Jake> directory, 'cvs remove' them from the old dir, and 'cvs add' Jake> them to the new dir. Agreed? Not quite. The point is that if the cp is done in the CVS repository, the new files will (a) automatically appear when you do cvs update -d and (b) preserve the old history (redundantly). And (c) somebody has to redirect the module aliases at the new repo dirs. Jake> But what about PUI? Won't it still, as Ville said, list the Jake> old package directories? Yes. We need to figure out how to handle that before Norbert releases new packages. Jake> BTW even if you like the idea of more granularity do we Jake> really need to list all the games libraries seperately? I Jake> think one package is really the better way to go, at least Jake> for games. I'm agnostic on that. Pre-PUI changes it seems reasonable, as long as we have a strategy for going in the opposite direction if it becomes feasible to have a "games" package that has no content of its own, but pulls in "mine" and "tetris" and "doctor". Real package dependencies should go a long way to handle this. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.