[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Native vs. non-native packages



Hi,

Am Mittwoch, den 21.01.2009, 14:44 -0600 schrieb John Goerzen:
> Joachim Breitner wrote:
> > 
> > you could develop it all in one branch, but before running
> > dpkg-buildpackage run a script that does (untested code)
> > 
> > UPSTREAM_VERSION=$(cat debian/changelog|some_grep_magic)
> > SOURCE_NAME=$(cat debian/control|some_grep_magic)
> > git archive --format=tar --prefix="$SOURCE_NAME-$UPSTREAM_VERSION" | \
> >     tar --file - --delete "$SOURCE_NAME-$UPSTREAM_VERSION/debian" | \
> >     gzip -9 > ../"$SOURCE_NAME_$UPSTREAM_VERSION".orig.tar.gz
> > 
> > This will place a nicely named tarball in the directory above, where
> > dpkg-buildpackage will find it and the only differences it will find are
> > the debian/ directory...
> > 
> > Does this sound viable?
> 
> That's an interesting idea, and makes me wonder:
> 
> perhaps I could just use the ./setup sdist output as the upstream
> tarball?  It would make sense on a number of levels, I think.

eh, right. I forgot that you are packaging cabal stuff :-)

Greetings,
Joachim

-- 
Joachim "nomeata" Breitner
Debian Developer
  nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
  JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil


Reply to: