From: Jeremy Olexa <olexa@cs.umn.edu>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] package.provided
Date: Sun, 16 Jul 2006 20:22:54 -0500 [thread overview]
Message-ID: <44BAE66E.8030605@cs.umn.edu> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Is there any other solution to the /etc/make.profile/package.provided
file? As we all know the /usr/portage/ dir gets wiped of custom files on
every sync. It seems kinda silly that there is a package.provided
solution but it gets wiped every time, so is there any other way to
accomplish the same thing on a more permanent term that I am not aware
of? The portage man page does not suggest anything else.
Thanks.
- --
Jeremy Olexa
(olexa@cs.umn.edu)
Office: EE/CS 1-201
CS/IT Systems Staff
University of Minnesota
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEuuZtFN7pD9kMi/URAqWbAJ4s/AUJfMhlRIHFMFF9Y+klSqMhJgCfWL1g
48mF2vMh2M7YlWumepiIVSk=
=PDsH
-----END PGP SIGNATURE-----
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2006-07-17 1:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 1:22 Jeremy Olexa [this message]
2006-07-17 1:30 ` [gentoo-user] package.provided Brett I. Holcomb
2006-07-17 1:37 ` Willie Wong
2006-07-17 7:43 ` Neil Bothwick
2006-07-18 4:28 ` Jeremy Olexa
2006-07-18 5:37 ` Donnie Berkholz
2006-07-21 3:35 ` proper use of package.provided (was: Re: [gentoo-user] package.provided) Jeremy Olexa
-- strict thread matches above, loose matches on Subject: below --
2007-05-08 15:23 [gentoo-user] package.provided Daniel Iliev
2007-05-08 15:39 ` Daniel Pielmeier
2007-05-08 18:10 ` Daniel Iliev
2007-05-08 20:13 ` Zac Medico
2007-05-09 9:22 ` Daniel Iliev
2007-05-09 13:53 ` Iain Buchanan
2007-05-09 14:48 ` Neil Bothwick
2008-01-08 12:35 Daniel Iliev
2008-01-08 13:07 ` Renat Golubchyk
2008-01-08 13:11 ` Alan McKinnon
2008-01-08 15:18 ` Daniel Iliev
2008-01-08 18:23 ` Alan McKinnon
2008-01-08 21:20 ` Daniel Iliev
2008-01-08 21:51 ` Dmitry S. Makovey
2008-01-08 21:54 ` Neil Bothwick
2008-01-08 21:40 ` Kenneth Prugh
2008-01-08 21:53 ` Neil Bothwick
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=44BAE66E.8030605@cs.umn.edu \
--to=olexa@cs.umn.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