[Pkg-jed-commit] r701 - jed/branches/0.99.19/debian

[Rafael Laboissiere]

* Jörg Sommer <joerg at alea.gnuu.de> [2007-05-17 13:45]:

> Rafael Laboissiere schrieb am Wed 16. May, 22:51 (+0000):
> > +  * Changed the upstream version numbering scheme, where the number after
> > +    "+pre" corresponds to the micro version of the unstable Jed
> > +    branch. [RL]
> > +  * debian/rules:
> > +    + Simplified the get-orig-source rule [JS]
> 
> Do you think we should mention such changes in the /Debian/ changelog?
> They aren't visible to and interesting for a package user.

Well, the change in the numbering scheme *_is_* visible to the user and she
may be interested to know the reason for the change.  At any rate, we are
targeting here our "power" users, which are using the package in
experiemental.

> > +    + The upstream version is obtained by parsing debian/changelog [RL]
> > +    + Remove *.orig.tar.gz in the clean rule
> 
> Why? We need it for a new debian version (-2) and I read in d-policy
> there is a project running that rebuilds the source two times: build
> clean build. Then the source build would fail.

This will delete the *.orig.tar.gz which is in the unpacked directory for
the package.  We need the the *.orig.tar.gz file which is at the directory
above.

> > -JED_VER=0.99.19~pre78
> > +JED_VER=${shell perl -ne '/\(([^-]+)-/; print $$1; last' < debian/changelog}
> 
> Doesn't make use $() instead of ${}?

Both are valid.  In the case above, $() fails because there are parentheses
in the command.

-- 
Rafael