Things we ought to do to improve our packaging

[Nikolaj Sjujskij]

Den 2013-08-08 10:29:56 skrev Matt Mackall <mpm at selenic.com>:

> On Wed, 2013-08-07 at 19:03 +0200, Dirkjan Ochtman wrote:
>> On Tue, Aug 6, 2013 at 8:53 PM, Matt Mackall <mpm at selenic.com> wrote:
>> > I think this also needs to be inclusive of builds for packaging  
>> systems
>> > (Debian, Ubuntu, RHEL, Centos, Solaris, Pypi, etc.). These actually
>> > suffer from more or less the same problems even though the  
>> distribution
>> > model is different. So we should be building nightlies and release
>> > builds for these systems and be more directly responsible for quality
>> > and timeliness here as well.
>>
>> On the other hand, I don't think there's anything here source-based
>> distro packaging has much to do with, right?
>
> I don't know, but I suspect there is. How does one grab the equivalent
> of a nightly on Gentoo?
  Basically users just install mercurial "from mercurial" (9999-version):

  % emerge -pvq mercurial
[ebuild   R   ] dev-vcs/mercurial-9999  USE="zsh-completion -bugzilla  
-emacs -gpg {-test} -tk" PYTHON_TARGETS="python2_7 (-python2_5) -python2_6"

  % hg version
Mercurial Distributed SCM (version 2.7+12-df2155ebf502+20130807)


> How long do I have to wait to install 2.7 if the packager is on vacation?
  I'm not sure what exactly do you mean by "have to wait", but bumping a  
package locally is a matter of these commands:
  # cd /usr/portage/dev-vcs/mercurial
  # cp mercurial-2.6.3.ebuild mercurial-2.7.ebuild
  # ebuild mercurial-2.7.ebuild digest

Provided nothing is changed in build system. Overlay (third-party repo)  
maintainer can copy ebuild and hack on it, then publish his/her work (like  
I maintain ebuilds for stable branch).

> Is there stuff that requires manual intervention from release to release  
> like adding new files?
  Er... Like what? Mercurial ebuild installs only a portion of files from  
contrib/, and automatic bump would miss new files worth installing, if  
that's what you mean.