public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "donnie berkholz" <donnie.berkholz@richmond.edu>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Re: gentoo-dev Digest 20 May 2003 21:51:40 -0000 Issue 126
Date: Tue, 20 May 2003 20:50:38 -0500	[thread overview]
Message-ID: <3ECADB6E.6050202@richmond.edu> (raw)
In-Reply-To: <1053467500.16326.ezmlm@gentoo.org>

But wouldn't it make sense to have a keyword in addition to 'system'
and 'world', something that amounted to 'emerge world-minus-system'?
This would allow easy administration of running all vital packages x86
and all non-system packages ~x86, for those of us who don't want to
destroy the system but just a few packages at a time. =)<br>
<br>
Donnie Berkholz<br>
<br>
<span type="cite"><a class="moz-txt-link-abbreviated" href="mailto:gentoo-dev-digest-help@gentoo.org">gentoo-dev-digest-help@gentoo.org</a> wrote:</span>
<p> </p>
<blockquote type="cite"
 style="border-left: thin solid blue; padding-left: 10px; margin-left: 0pt;">
  <p>
  <table noborder="" cellpadding="0">
    <tbody>
      <tr>
        <td nowrap="nowrap" align="right" valign="top"><b>Subject:</b></td>
        <td valign="top"><b>Re: [gentoo-dev] MySQL 4 still marked
unstable?</b></td>
      </tr>
      <tr>
        <td nowrap="nowrap" align="right" valign="top"><b>Date:</b></td>
        <td valign="top">10:23 AM</td>
      </tr>
      <tr>
        <td nowrap="nowrap" align="right" valign="top"><b>From:</b></td>
        <td><a
 href="mailto:g2boojum@gentoo.org">Grant
Goodyear &lt;g2boojum@gentoo.org&gt;</a></td>
      </tr>
      <tr>
        <td nowrap="nowrap" align="right" valign="top"><b>To:</b></td>
        <td><a
 href="mailto:veldy@veldy.net">"Thomas
T. Veldhouse" &lt;veldy@veldy.net&gt;</a></td>
      </tr>
      <tr>
        <td nowrap="nowrap" align="right" valign="top"><b>cc:</b></td>
        <td><a href="mailto:gentoo-dev@gentoo.org">gentoo-dev@gentoo.org</a></td>
      </tr>
    </tbody>
  </table>
  </p>
  <p><tt> &gt; As far as protecting ebuilds goes, I was actually
referring to the ability <br>
&gt; to mix keywords (i.e. x86 and ~x86) and still upgrade world in an
easy <br>
&gt; manner.&nbsp; I think there should be two source or ebuild systems, one
for the <br>
&gt; base system and one for the "ports".&nbsp; In this manner one can keep
the <br>
&gt; software up to date and yet keep the system stable.&nbsp; I am thinking
along the <br>
&gt; lines of the freebsd ports system, but with ebuilds instead. <br>
  <br>
Clearly "-U" needs to get fixed, and I know that carpaski has plans to <br>
do just that.&nbsp; It's worth noting, though, that one of the great <br>
strengths of Gentoo Linux is that there is _no_ separation between <br>
"system" and "ports" as there is in the bsd world; all packages are <br>
handled on an equal footing.&nbsp; That lack of separation is one of the <br>
things that makes Gentoo so useful as a metadistribution -- somebody
who <br>
needs a custom base profile can easily create one. <br>
  <br>
-g2boojum- <br>
-- <br>
Grant Goodyear <a class="moz-txt-link-rfc2396E" href="mailto:g2boojum@gentoo.org">&lt;g2boojum@gentoo.org&gt;</a> </tt></p>
</blockquote>
<span></span>


--
gentoo-dev@gentoo.org mailing list


           reply	other threads:[~2003-05-21  1:54 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1053467500.16326.ezmlm@gentoo.org>]

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=3ECADB6E.6050202@richmond.edu \
    --to=donnie.berkholz@richmond.edu \
    --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