From: Willie Wong <wwong@Princeton.EDU>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] why is Joe part of 'system' ?
Date: Sun, 4 Sep 2005 14:26:56 -0400 [thread overview]
Message-ID: <20050904182656.GA18650@princeton.edu> (raw)
In-Reply-To: <20050904174232.GD7622@sympatico.ca>
On Sun, Sep 04, 2005 at 01:42:32PM -0400, Philip Webb wrote:
> > I'd put money on it being considered part of system
> > because it provides virtual/editor, which is part of system.
>
> In /usr/portage/profiles/base/virtuals , it says
>
> virtual/editor app-editors/nano
>
> there's no mention of Joe.
>
In the ebuild it specifies
PROVIDE="virtual/editor"
the virtual/editor thing in the profiles just specifies that the
default install will use app-editors/nano to satisfy the
virtual/editor requirement in system. If you have ANYTHING at all that
provides virtual/editor, it will satisfy the system. But at the same
time, if you want to unmerge anything that provides virtual/editor,
the warning will come up.
For example, currently, on my desktop,
[02:21 PM]wwong ~ $ emerge search nano
Searching...
[ Results for search key : nano ]
[ Applications found : 4 ]
* app-editors/nano
Latest version available: 1.3.7
Latest version installed: [ Not Installed ]
Size of downloaded files: 985 kB
Homepage: http://www.nano-editor.org/
Description: GNU GPL'd Pico clone with more functionality
License: GPL-2
[02:22 PM]wwong ~ $ cat /usr/portage/profiles/base/virtuals | grep editor
virtual/editor app-editors/nano
virtual/emacs app-editors/emacs
virtual/xemacs app-editors/xemacs
[02:19 PM]wwong proto-gen $ emerge --pretend virtual/editor
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild R ] app-editors/gvim-6.3.084
So... although nano is the "default editor" it is not installed on my
system. And I have at least gvim to satisfy the virtual/editor
requirements in system (though I usually use vim, which also satisfies
the requirement). In fact, if you
grep "virtual/editor" /usr/portage/app-editors/*/*ebuild
you'd see that easyedit, elvis, emacs, gvim, jed, joe, nano, ne, nvi,
teco, vile, vim, xemacs all provide that function.
So in short, just go ahead and unmerge Joe if you aren't going to use
it.
W
--
"There was a point to this story, but it has temporarily
escaped the chronicler's mind."
- This line perhaps best sums up the whole book.
Sortir en Pantoufles: up 23 days, 21:21
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-04 18:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-04 14:30 [gentoo-user] why is Joe part of 'system' ? Philip Webb
2005-09-04 14:46 ` Mark Knecht
2005-09-04 16:31 ` Edward Catmur
2005-09-04 16:33 ` Mike Williams
2005-09-04 17:42 ` Philip Webb
2005-09-04 18:04 ` [gentoo-user] " Sven Köhler
2005-09-04 18:04 ` Sven Köhler
2005-09-04 18:19 ` [gentoo-user] " Mike Williams
2005-09-04 19:23 ` Holly Bostick
2005-09-05 8:32 ` Philip Webb
2005-09-05 9:16 ` Nagatoro
2005-09-05 11:14 ` Holly Bostick
2005-09-05 11:29 ` Mike Williams
2005-09-05 11:36 ` Jason Stubbs
2005-09-05 11:44 ` Holly Bostick
2005-09-05 12:27 ` Jason Stubbs
2005-09-04 18:26 ` Willie Wong [this message]
2005-09-04 19:01 ` Philip Webb
2005-09-04 19:56 ` Mariusz Pękala
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=20050904182656.GA18650@princeton.edu \
--to=wwong@princeton.edu \
--cc=gentoo-user@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