On Tue, 26 Aug 2008, Lucas Nussbaum wrote:
This idea cames up on a regular basis. I think that the consensus is
that it's better to simply use the Debian archive as VCS. When you
change/fix something in an orphaned package, just upload ;)
Well, OK, this might make some sense if you just not intend to care
more for a package than a single upload. On the other hand there is
collab-maint/orphaned - so people seem to seek for a pragmatic solution.
Making the process of doing QA uploads more complex, by asking
care-takers to look at a VCS first, is IMHO not a good thing.
I trust your experience. The precondition for keeping a package in
VCS is that debian/control contains the relevant fields - if not
nobody will ever know where to look.
Of course, when a package has been adopted, and there's no obvious team
to maintain it, the best solution is probably to use collab-maint to
maintain it. You didn't know about collab-maint? Maybe we need to
communicate a bit more about this.
Definitely!
I admit I do not very well in keeping track of all the nice tools that
are developed by fellow DDs and perhaps I do not read announcements carefully
enough (or just do not understand every consequence of an announcemant for
my daily or future work). There is just no chance to cope with all this
stuff in my day-to-day work. But I strongly assume that this is true for
the waste majority of DDs and we should increase the communication channels.
Kind regards
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
