Re: CVS location for dselect documentation for beginners
Josip Rodin <firstname.lastname@example.org> writes:
> The dselect beginners guide is the one document in the b-f CVS tree that
> _really_ doesn't belong there: if you remove the dependencies on the b-f
> files from the header, you'll notice just a few missing tags, none of which
> are even borderline important to the document itself, and all of them
> trivial to arrange in a separate tree.
I agree completely. I wondering though if this should go in the DDP
CVS area, or even perhaps in the dselect package. If in the DDP CVS
area, should it be packaged as well? I think it will need to be...
> I'm thinking of moving it out into the DDP tree where it will likely get
> some more attention and tender loving care ;) Any suggestions for preserving
> the history? cp the ,v files, or just ignore that and cvs remove here + cvs
> add there, with a pointer to the old place just in case anyone cares?
I would suggest doing a checkout from the head, then copy those files
over and do a CVS import from that, then start adapting it for being
> The situation is similar with the release notes, which just need a few tags
> to be able to skip some info for architectures recently released.
> The installation manual needs entities from the po files of debootstrap, but
> the document will likely need a rewrite for debian-installer, and I'm not so
> sure if it will be doable in exactly the same way with d-i. In any case, we
> can write scripts to obtain the data from wherever it is.
Yup. I already have some code that uses apt-get to download pkgs it
needs (e.g., ASCII version of relevant man pages).
Is anyone responsible for the rewrite of the install manual for d-i?
I'd prefer not to take it since I'd like to put my attention on
developers-reference, doc-base, and my bugs for a while...
...Adam Di Carlo..<email@example.com>...<URL:http://www.onshored.com/>