On Thu, Aug 02, 2018 at 10:33:14PM -0700, Paul Hardy wrote:
> On Thu, Aug 2, 2018 at 9:14 AM, Osamu Aoki <[email protected]> wrote:
...
> >> Running "autoreconf -ivf" as described in Section 5.16.1 will create
> >> a new INSTALL file even if one existed.i
> >
> > As written there, this is run by the upstream.
>
> Well, building in debian/rules with autoreconf will run that too.
Very true. (I was not thinking clearly)
> Actually, I don't know if running automake with "foreign" strictness
> re-creates INSTALL. I have only tried automake with "gnu" strictness.
Let me think a bit when I have time.
...
> > Maybe, somewhere in 5.16. Upstream build systems, I should add some
> > reminder to test build package.
> >
> > autotools: make distcheck
> > cmake: ?
> > setup.py: ?
> >
> > Let me think a bit on this.
>
> I have never used CDBS, cmake, etc., so I don't know how they work. I
> think a quick mention of using distcheck as a warm-up exercise for
> pbuilder (for example) is useful, because that lets a packager know
> that the package builds correctly when builddir is not the same as
> srcdir.
>
> Maybe it is worth mentioning that in some more general way in the
^^^^^^^^^^^^^^^^^^^^^^^
> beginning. Most people packaging for Debian for the first time are
^^^^^^^^^
I think you have very good point here.
> probably coming from an environment where they only cared about
> building for the single architecture that they were using.
I think I put some reminder already but I agree with your thought. I
think we need reminder for:
* Multi-arch
* Reproducible build
* Boot straping
...
Regards,
Osamu
> Thanks,
>
>
> Paul Hardy
