public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Per Wigren <wigren@home.se>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Renaming ebuilds...
Date: Wed, 26 Mar 2003 00:57:41 +0100	[thread overview]
Message-ID: <200303260057.43296.wigren@home.se> (raw)

We need a method to rename and move ebuilds... For example 
dev-perl/Mail-SpamAssassin does not belong in dev-perl... It really should be 
net-mail/spamassassin instead.. I don't think anyone using spamassassin cares 
that it is written in Perl...
Another one is x11-themes/redhat-artwork which should be called bluecurve 
instead... Yes, that one is my fault because I submitted it as redhat-artwork 
a long time ago.. ;)  But anyway..   How about a special variable in the 
ebuilds called OBSOLETES?
An example:
We move dev-perl/Mail-SpamAssassin/Mail-SpamAssassin-2.52.ebuild to 
net-mail/spamassassin/spamassassin-2,52,ebuild and add the line:
OBSOLETES="dev-perl/Mail-SpamAssassin"

A user who has Mail-SpamAssassin installed and run "emerge -u world" would 
then "upgrade" dev-perl/Mail-SpamAssassin to net-mail/spamassassin..

This could also be used in other places.. Example:

net-www/galeon-1.3.0.ebuild: (when it is released)
OBSOLETES="<=net-www/galeon-cvs-20030324"


Does this sound sane? ;)
Maybe it's already implemented in some way? I admit it was a LONG time ago I 
wanted this functionality last time, but it wasn't implemented by then...

Regards,
Per Wigren

--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2003-03-26  0:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-25 23:57 Per Wigren [this message]
2003-03-26  0:16 ` [gentoo-dev] Renaming ebuilds Jon Portnoy
2003-03-26 23:28 ` Abhishek Amit
2003-03-27  5:20   ` Per Wigren
2003-03-27 12:59     ` Alastair Tse
2003-03-27 13:00     ` leahcim
2003-03-29 16:11   ` Paul de Vrieze

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=200303260057.43296.wigren@home.se \
    --to=wigren@home.se \
    --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