[arch-dev-public] Rewriting dbscripts (packagers should read this!)
allan at archlinux.org
Mon Sep 30 22:29:55 EDT 2013
On 01/10/13 03:36, Florian Pritz wrote:
> 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.
1) Please use "all" rather than "any" when referring to all
architectures. "any" already has a defined use.
2) Does this involve stopping the use of repo-add? I know of at least
two projects that aim at replacing it, although none have been proposed
on pacman-dev yet. I think it is important for something like repo-add
to be tied to pacman, but we could add an option to update an extracted
directory (e.g. git repo) rather than a tarball if that would be useful.
(Aside: please consider a separate repo for debug packages. The [extra]
and [community] databases are already large enough.)
More information about the arch-dev-public