From 9d9e64508186e5f9efbe45302134cd709b25e47b Mon Sep 17 00:00:00 2001 From: Ludovic Courtès Date: Sun, 4 Nov 2012 21:44:42 +0100 Subject: distro: Go for one module per package. The alternative, which was to use one module per category, would probably not scale well. First, because many packages could fall into several categories (does GnuTLS go into "networking", "security", or "libraries"?). Second, because that could easily lead to circular dependencies among modules ("security" and "networking" depend on each other, etc.) * distro/packages/databases.scm: Rename to... * distro/packages/recutils.scm: ... this. * distro/packages/typesetting.scm: Rename to... * distro/packages/lout.scm: ... this. * Makefile.am (MODULES): Adjust accordingly. * po/POTFILES.in: Likewise. --- po/POTFILES.in | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'po') diff --git a/po/POTFILES.in b/po/POTFILES.in index 887b7106ee..fcc84f32f0 100644 --- a/po/POTFILES.in +++ b/po/POTFILES.in @@ -1,9 +1,9 @@ # List of source files which contain translatable strings. distro.scm distro/packages/base.scm -distro/packages/databases.scm distro/packages/guile.scm -distro/packages/typesetting.scm +distro/packages/lout.scm +distro/packages/recutils.scm guix/ui.scm guix-build.in guix-download.in -- cgit v1.2.3