Re: build from CVS and upload
olet@ifi.uio.no (Ole J. Tetlie) writes:
> > I build my packages from CVS and it works very good. But
> > now I don't know, if I can upload the resulting .tar.gz.
> >
> > Since the CVS is the upstream CVS and the debian directory
> > is already in, it would be the best solution. But somehow
> > I interprete the policy in the way, that just debian-specific
> > packages can use this upload methode.
>
> This can be done
> "if the package is specially prepared for Debian or the Debian maintainer
> is the same as the upstream maintainer", according to the packaging manual.
> I'd say that you can be considered the upstream maintainer (or at least
> an upstream maintainer, since you have write access), so it should be ok.
>
> Since many packages now can be made from cvs sources, and this is a very
> reasonable thing to do¹, I think the manual should be changed to explicitly
> say that this situation is ok.
Hmm. I'm not totally clear about what you're saying here.
The first, more general point I would like to make is that you should
*not* ship the CVS subdirs as part of your .diffs or as part of the
.orig.tar.gz. In other words, the CVS subdirs should not be part of
the distributed source debian package.
What I generally do when I'm distributing software out of CVS, whether
it's debian or not, is first 'cvs tag <some_tag>' then 'cvs export -r
<some_tag> <module>'.
The second point is that Manoj's excellent cvs-buildpackage pacakge is
an excellent tool for anyone using CVS and maintaining packages. Use
it, live it. And laugh at all the other schlubs when you'er able to
branch off a version for hamm and one for slink and maintain both of
them!
.....A. P. Harris...apharris@onShore.com...<URL:http://www.onShore.com/>
--
To UNSUBSCRIBE, email to debian-mentors-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: