[PATCH 4 of 6 packaging] builddeb: new script for building a deb package
pierre-yves.david at ens-lyon.org
Fri May 8 16:33:00 CDT 2015
On 05/08/2015 10:10 AM, Augie Fackler wrote:
> # HG changeset patch
> # User Augie Fackler <augie at google.com>
> # Date 1430932434 14400
> # Wed May 06 13:13:54 2015 -0400
> # Node ID 25e90eb8e6dd9a142d52128d13584d2d99147d7f
> # Parent 0232c9960ca7e5506ab1ec1c73e1c245de547edc
> builddeb: new script for building a deb package
> Future work will allow us to use docker to build debs.
> Right now this doesn't install any config files. I plan to do that as
> a followup, but getting something basic and working checked in seems
> like more of a priority than getting everything done in one big step.
> This also does not create a source deb yet. I haven't looked into that
not that the centos rules are apparently nice enough to build package
-and- produce a valid package repositories that can be used as a source.
That would be nice to have that for debian too.
> Note that this declares incompatibility with the `mercurial-common`
> package. It's typical for debian packages to be split between
> architecture-independent bits and native bits, meaning the python bits
> downstream live in mercurial-common and the c extension bits live in
> mercurial. We don't do that because we want to (ideally) give users a
> single deb file to install.
This sounds like a bad goal. Ideally, we should be able to produce
package compatible with what Debian is doing, and gracefully integrating
in there naming scheme.
I do not believe downloading multiple .deb will be a show stopped. I've
doing that on a regular basis from other project nightly build.
The patch are accepted anyway to move the topic forward. I'll lets
people who know something about debian packaging make comment for follow up.
More information about the Mercurial-devel