I have a question about cvs-buildpackage.
I was surprised to see that all of the upstream .orig.tar.gz is
injected into my CVS repository. I was expecting that the CVS
repository would only hold those files modified or added for the
debian build (only those files for which there are entries in th
The policy manual does not have much to say about subsections. 2.1.7
simply says "Please check the current Debian distribution to see which
sections are available." Is there a document discussing the purpose
of current subsections?
I suppose that subsection choice is usually obvious, but the use
the help. I have heard this expressed before, and it
was certainly true for me; the packaging process seems rather
confusing at first, but it is actually quite easy once you figure
things out. (Yeah, yeah, I know that these were two really simple
packages -- no executables, only info files -- but now I am ready for
more something more complicated.)
Kirk Hilliard
d doing-it-yourself
just implementing "debstd" line in debian/rules? If that is the case,
then perhaps the outline in /usr/doc/debmake/HOWTO.first_time applies
to the "by hand" method as well. If not, then I would love to see
such an outline.
Kirk Hilliard
tlogin ())) {
and getlogin seems to work for me:
$ perl -le 'print getlogin()'
kirk
$
Does this have something to do with fakeroot?
Thats all for now. I think that my packages might be ready for
upload, but I would sure appreciate some answers to these questions.
Thanks,
Kirk Hilliard
5 matches
Mail list logo
