From: Nirbheek Chauhan <nirbheek@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [RFC] Improve policy of stabilizations
Date: Fri, 6 Nov 2009 22:36:05 +0530 [thread overview]
Message-ID: <8b4c83ad0911060906j992c037pb76eaa4c65de3680@mail.gmail.com> (raw)
In-Reply-To: <20091106144535.GT1150@gentoo.org>
On Fri, Nov 6, 2009 at 8:15 PM, Fabian Groffen <grobian@gentoo.org> wrote:
> Sounds like we could benefit from the "noarch" approach known in the RPM
> world, such that all these packages can also be immediately keyworded
> and stabilised for all arches. Would greatly simplify things for a
> great deal of packages, maybe?
>
This is a good idea; themes, wallpapers, fonts, game-data (stuff that
mostly installs into /usr/share) could easily fall in this category. A
lot of python modules are arch-independant as well (upstream has been
thinking of splitting the install structure to put such things in
/usr/share/python2.6/<etc>).
Examples of packages:
gnome-extra/gnome-games-extra-data
x11-themes/gnome-icon-theme
kde-base/kdebase-wallpapers
games-fps/quake3-data
app-text/poppler-data
media-fonts/dejavu
--
~Nirbheek Chauhan
Gentoo GNOME+Mozilla Team
next prev parent reply other threads:[~2009-11-06 17:06 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-01 16:36 [gentoo-dev] [RFC] Improve policy of stabilizations Arfrever Frehtes Taifersar Arahesis
2009-11-01 16:55 ` Mart Raudsepp
2009-11-01 18:19 ` Richard Freeman
2009-11-01 20:21 ` Petteri Räty
2009-11-01 21:16 ` [gentoo-dev] " Ryan Hill
2009-11-02 14:17 ` Christian Faulhammer
2009-11-02 15:23 ` Markos Chandras
2009-11-03 18:10 ` Christian Faulhammer
2009-11-04 12:36 ` Ben de Groot
2009-11-04 12:50 ` Christian Faulhammer
2009-11-04 18:01 ` Tobias Klausmann
2009-11-04 20:49 ` Nirbheek Chauhan
2009-11-04 21:02 ` Joseph Jezak
2009-11-05 3:48 ` Ryan Hill
2009-11-05 9:17 ` Tobias Klausmann
2009-11-05 20:12 ` Petteri Räty
2009-11-06 3:06 ` Joseph Jezak
2009-11-06 14:18 ` Nirbheek Chauhan
2009-11-06 14:45 ` Fabian Groffen
2009-11-06 17:06 ` Nirbheek Chauhan [this message]
2009-11-06 17:08 ` Nirbheek Chauhan
2009-11-07 5:13 ` Ryan Hill
2009-11-06 22:07 ` Zac Medico
2009-11-07 3:36 ` Arfrever Frehtes Taifersar Arahesis
2009-11-07 14:54 ` Peter Volkov
2009-11-07 20:49 ` Zac Medico
2009-11-08 0:12 ` Nirbheek Chauhan
2009-11-08 9:31 ` Petteri Räty
2009-11-08 12:55 ` Peter Volkov
2009-11-09 2:34 ` Zac Medico
2009-11-08 9:05 ` Fabian Groffen
2009-11-08 12:53 ` Peter Volkov
2009-11-06 22:52 ` Rémi Cardona
2009-11-07 7:22 ` Hans de Graaff
2009-11-06 16:00 ` Kent Fredric
2009-11-06 17:00 ` Nirbheek Chauhan
2009-11-07 14:14 ` Tobias Klausmann
2009-11-05 10:52 ` Duncan
2009-11-06 17:18 ` Christian Faulhammer
2009-11-06 17:15 ` Christian Faulhammer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8b4c83ad0911060906j992c037pb76eaa4c65de3680@mail.gmail.com \
--to=nirbheek@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox