Things we ought to do to improve our packaging

[Nikolaj Sjujskij]

Den 2013-08-19 02:29:49 skrev Matt Mackall <mpm at selenic.com>:

> On Sun, 2013-08-18 at 16:44 +0200, Dirkjan Ochtman wrote:
>> On Thu, Aug 8, 2013 at 8:29 AM, Matt Mackall <mpm at selenic.com> wrote:
>>> I don't know, but I suspect there is. How does one grab the equivalent
>>> of a nightly on Gentoo? How long do I have to wait to install 2.7 if
>> the
>> > packager is on vacation? Is there stuff that requires manual
>> > intervention from release to release like adding new files?
>>
>> As Nikolaj mentioned, you can trivially build packages from your
>> public repo's tip. There are two packagers, so you might have to wait
>> a little bit, but it's only a filename move away (in an overlay) if
>> you want it badly (e.g. no actual building). No intervention is
>> generally required for version bumps.
>
> Ok, so it's fairly painless. Let's flip the question around: is there
> any reason we should NOT be doing automated nightly Gentoo builds to
> spot problems, given how easy it is?
  What for? I don't think it's a good idea to push nightlies into even  
testing branch, and people who feel inclined to follow Mercurial  
development are welcome to use "live" ebuild, which is only one command  
away.

> This would have presumably spotted something like this before release:
>
> http://www.bz.selenic.com/show_bug.cgi?id=4010
>
> ..and perhaps real problems as well.
  If my memory serves me right,  
http://www.bz.selenic.com/show_bug.cgi?id=3482 was caught by me running  
exactly "live" Mercurial from our main tree. But I don't think snapshots  
are suitable even for "unstable" branch, and those who want bleeding edge  
already have it.