public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] intention for kde-themes eclass
Date: Tue, 14 Jun 2005 04:18:02 +0200	[thread overview]
Message-ID: <03D40B78-BB55-40EA-A83B-2D32A70FE64A@gentoo.org> (raw)
In-Reply-To: <20050614193351.79655146@localhost>

On Jun 14, 2005, at 12:33 PM, Chris White wrote:

> kde-look.org is a site that hosts various kde themes to change the  
> look and feel of the kde desktop.

Well actually some of the things I've done as an "external" was  
maintaining a series of ebuilds for themes, splashscreens and stuff  
like that.
I also tried submitting a couple of them initially, but as I was  
told, portage isn't the place where such things belong.
I think this is right. There are already too many things in portage  
as is now, and not all users like syncing the whole tree everytime.  
We have patches there which are for software rarely used.
Maybe adding the eclass and then maintaining an overlay for that can  
be better... not sync-ed but tarballed and who wants to update it, it  
just need to redownload it.

That's just my opinion.

-- 
Diego
-- 
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-06-14  2:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-14 10:33 [gentoo-dev] intention for kde-themes eclass Chris White
2005-06-14  2:18 ` Diego 'Flameeyes' Pettenò [this message]
2005-06-14  2:19 ` Brian Jackson
2005-06-14 12:04   ` Gregorio Guidi
2005-06-14  4:57 ` Shyam Mani
2005-06-14  9:22   ` Michael Cummings
2005-06-14  9:49     ` Diego 'Flameeyes' Pettenò
2005-06-15  1:06 ` kde-theme.py (formerly [gentoo-dev] intention for kde-themes eclass) Chris White
2005-06-14 21:39   ` Paul de Vrieze
2005-06-15 13:57     ` Chris White

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=03D40B78-BB55-40EA-A83B-2D32A70FE64A@gentoo.org \
    --to=flameeyes@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