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

Re: Bootstrapping alex



On Tue, Dec 22, 2015 at 10:46:48AM +0100, Joachim Breitner wrote:
> Am Dienstag, den 22.12.2015, 02:52 +0000 schrieb Colin Watson:
> > Now that we have build profiles, I've implemented and tested stage1
> > build profile support for all of happy, alex, and uuagc, and uploaded
> > all those to unstable since the current ghc transition is out of the
> > way.  This should help out porters a little bit without
> > inconveniencing normal development.
> 
> Thanks for that. There is more demand for build profiles, and an actual
> use case now:
> 
> Am Dienstag, den 22.12.2015, 10:24 +0100 schrieb John Paul Adrian Glaubitz:
> > Test build on armhf went without problems. Now building the actual
> > package for armel. After that, we will need to build and upload
> > hscolour manually on armel since there is still a circular build
> > dependency (might be an idea to resolve it with the help of
> > build profiles, for example).
> 
> Do you think this can also be fixed using build profiles?

I don't think this is actually a problem in practice because hscolour is
in ghc's Build-Depends-Indep, not Build-Depends.  Perhaps Adrian forgot
to use dpkg-buildpackage -B rather than -b?

> And are build profiles actually already supported by our auto-building
> infrastructure? If not, what is the practical gain today?

Our buildds support them to the extent that they correctly build with
the empty set of profiles, but not otherwise.  sbuild supports building
a package with a given set of build profiles, and I believe some tools
specialised for bootstrapping support them.

However, the practical gain is that it gets the knowledge of how to do
this kind of bootstrapping operation out of people's heads and into code
where porters can do it fairly easily without needing to ask us for the
details.

-- 
Colin Watson                                       [cjwatson@debian.org]


Reply to: