On Thu, Mar 12 2009, Russ Allbery wrote:
>
> I personally use the same technique that Steve uses for the packages that
> I maintain that need to be repacked, and I'm having a failure of
> imagination for how I could do it the way that Manoj describes.
Hmm. Let me see if I can elucidate. Here is my work flow.
a) Run a upstream version check from cron, which mails me if there are
new upstream versions of something I have.
b) If there is a new upstream version, cd checked out dir
1. No munging required: use uscan --rename --verbose to get the
latest source.
2. Munging needed. Run get-orig-source to get the latest upstream
source via uscan; and munge it as needed to create the
orig.tar.gz file
c) Proceed as per:
http://www.golden-gryphon.com/blog/manoj/blog/2009/02/25/A_day_in_the_life_of_a_Debian_hacker/
Is this so very different from what people do? Some times I do
not package every upstream version, if they are coming in rapid
succession, or if I find some version unfit for Debian -- but in any
case, the majority of the time I want to package the very latest
upstream version.
manoj
--
"The world is coming to an end. Please log off." Bob Irwin
(bir...@ficc.ferranti.com)
Manoj Srivastava <sriva...@debian.org> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
