[arch-dev-public] Rewriting dbscripts (packagers should read this!)

Eric Bélanger snowmaniscool at gmail.com
Tue Oct 1 09:07:03 EDT 2013

On Mon, Sep 30, 2013 at 1:36 PM, Florian Pritz <bluewind at xinu.at> wrote:

> Hi,
> After having read the recent git thread I've come to the conclusion that
> we should rework dbscripts before we start working on the package
> backend (although my proposal works better with git because it uses tags).
> TLDR: You should care and read it. If you don't I won't care if you
> later miss features that contradicts my proposal.
> Note: The text below is more or less a cleaned up brain dump so it's
> probably not complete and possibly confusing. If so, please tell me. I'm
> also open for discussion via irc as long as the important points are
> later sent to the ML.

I would like to keep the support for directly supplying the commit message:
(commitpkg "update to version 1.2.3").  It's useful to have the commit
message in the bash history when doing same change to several packages, e.g
upstream update, soname rebuild, etc.

Will the new dbscripts support split packages with differents arch (it
seems to be the case from the pacman example)? For example, most docs
packages don't use the 'any' arch because the current dbscripts don't
support it.  If we could support, it we would reduce server disk space and


More information about the arch-dev-public mailing list