From: Mikael Hallendal <hallski@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] gkrellm extra's
Date: 28 Dec 2001 19:42:25 +0100 [thread overview]
Message-ID: <1009564945.14121.16.camel@zoidberg> (raw)
In-Reply-To: <1009555882.24689.0.camel@djamil>
[-- Attachment #1: Type: text/plain, Size: 2781 bytes --]
fre 2001-12-28 klockan 17.11 skrev djamil essaissi:
> hey guys;
> well, i see that ... beeing all humans seeing things differently ... for
> example gnomedb can see it self in gnome or office or x11-misc ...or
> whatever it's just an example maybe a poor one ...
> so why not making symbolic links so we have ebuils "A" in many locations
> ? ...
> is it too much to maintain ?!
Well, for one thing it would be unmaintainable since ebuilds would start
pointing to them by symbolic links and stuff. Next is that symbolic
links doesn't work in CVS so it's undoable.
Possibility to do 'emerge gnome-db' or 'efind gnome-db' or something
would be better.
Regards,
Mikael Hallendal
>
> On Fri, 2001-12-28 at 16:51, Mikael Hallendal wrote:
> > fre 2001-12-28 klockan 16.22 skrev Joshua Pierre:
> > > Hi Guys,
> > >
> > > Just browsing my Portage tree in a dull moment and I noticed that gkrellm plugins/extra's seem to be in several different places throughout Portage. A few exampls follow:
> >
> > Hi!
> >
> > I've been meaning to take care of this sometime. Just haven't gotten
> > around to it.
> >
> > They will all move to x11-misc or app-misc (probably x11-misc)
> >
> > Regards,
> > Mikael Hallendal
> >
> > >
> > > x11-misc/gkrellmtime
> > > net-misc/gkrellmwireless
> > > media-sound/gkrellmms
> > > app-admin/gkrellm
> > >
> > > I am not sure if this should all go under app admin, just looks like it's a bit hard to track where things are without going:
> > >
> > > # locate gkrellm | more
> > >
> > > Also, just wondering what gift is, there is an ebuild there for it but it has no DESCRIPTION line. After seeing this I got thinking about an ebuild audit where all ebuilds are updated and confirmed, this sound like a good idea?
> > >
> > > Anyway, just wanted on check on that gkrellm issue then the rest spewed out :-)
> > >
> > > --
> > > Joshua Pierre
> > > Developer & Release Technician
> > > Themes.Org -- Open Source Interface Enhancement
> > > _______________________________________________
> > > gentoo-dev mailing list
> > > gentoo-dev@gentoo.org
> > > http://lists.gentoo.org/mailman/listinfo/gentoo-dev
> > >
> > --
> >
> > Mikael Hallendal
> > Gentoo Linux Developer, Desktop Team Leader
> > CodeFactory AB, Stockholm, Sweden
> >
> --
> Djamil ESSAISSI
> Tel:01.58.64.22.44 - Fax:01.58.64.26.81
> Systeme Administrateur / Support Technique
> www.francexpress.com - www.serveur-express.com
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>
--
Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-12-28 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-28 15:22 [gentoo-dev] gkrellm extra's Joshua Pierre
2001-12-28 15:51 ` Mikael Hallendal
2001-12-28 16:11 ` djamil essaissi
2001-12-28 18:42 ` Mikael Hallendal [this message]
2001-12-28 22:26 ` Geert Bevin
2001-12-28 16:21 ` Jens Blaesche
2002-01-01 6:56 ` MIkael Hallendal
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=1009564945.14121.16.camel@zoidberg \
--to=hallski@gentoo.org \
--cc=gentoo-dev@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