public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] portage-2.2.0_alpha38 & --depclean
Date: Tue, 07 Jun 2011 19:01:16 -0500	[thread overview]
Message-ID: <4DEEBBCC.6070301@gmail.com> (raw)
In-Reply-To: <201106080032.03877.alan.mckinnon@gmail.com>

Alan McKinnon wrote:
> OK, now we're tracking.
>
> In the specific case of less, the answer is self-evident - it isn't needed. A
> dev would just know that. More likely, he would assume he knows that.
>
> In the general case, they suck their thumbs and guess. Some think more than
> others before they guess, they should all do some basic tests to catch severe
> errors before committing changes and additions, and all of them rely on
> unstable users finding other oddities and bugs.
>
> flameeyes gave some hints and clues into how this works on his blog recently:
>
> http://blog.flameeyes.eu/2011/05/25/psa-packages-failing-to-install-with-new-
> openrc-based-stages-missing-users-and-groups
>
> It's specific to openrc, but if you follow his blog it's easy to read between
> the lines to see what he's getting at usually.
>
> I don't think I've ever met a dev that releases code any other way :-)
>
> None of the above is fact and all of it is my opinion but I do think I'm close
> to the mark.
>
>    

OK.  This is todays version.

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   *] sys-apps/portage-2.2.0_alpha38  USE="(ipc) less%* 
-build -doc -epydoc -python2 -python3 (-selinux)" LINGUAS="-pl" 810 kB
[ebuild   R    ] net-print/hplip-3.10.9-r1  USE="X hpcups kde libnotify 
parport (policykit) qt4 -acl% -doc -fax -hpijs -minimal -scanner -snmp 
-static-ppds (-udev-acl%)" 21,307 kB

So, they added a USE flag to get less back on track.  Does that mean we 
can all remove it from world now?

This is not just for me but for others as well.

Dale

:-)  :-)



  reply	other threads:[~2011-06-08  0:02 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07  9:10 [gentoo-user] portage-2.2.0_alpha38 & --depclean Alan McKinnon
2011-06-07  9:34 ` Dale
2011-06-07 10:54 ` Neil Bothwick
2011-06-07 11:36   ` Alan McKinnon
2011-06-07 20:33     ` Alan McKinnon
2011-06-07 20:51       ` Mark Knecht
2011-06-07 21:07         ` Alan McKinnon
2011-06-07 21:39           ` Mark Knecht
2011-06-07 22:32             ` Alan McKinnon
2011-06-08  0:01               ` Dale [this message]
2011-06-08  0:22               ` Mark Knecht
2011-06-07 23:09             ` Neil Bothwick
2011-06-08  0:20               ` Mark Knecht
2011-06-08  0:33                 ` Dale
2011-06-08  0:39                   ` Mark Knecht
2011-06-08  1:12                     ` Dale
2011-06-08 11:15                     ` Albert Hopkins
2011-06-08 14:09                       ` Mark Knecht
2011-06-08 14:27                         ` Albert Hopkins
2011-06-08 14:37                           ` Mark Knecht
2011-06-08 15:38                             ` Albert Hopkins
2011-06-08 15:59                               ` Mark Knecht
2011-06-08  7:53                 ` Neil Bothwick
2011-06-07 11:23 ` Todd Goodman
2011-06-07 11:39 ` Indi
2011-06-07 12:55 ` Mark Knecht
2011-06-07 23:08   ` Walter Dnes
2011-06-07 23:54     ` Alan McKinnon
2011-06-08  0:03       ` Dale
2011-06-08  0:15         ` Alan McKinnon

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=4DEEBBCC.6070301@gmail.com \
    --to=rdalek1967@gmail.com \
    --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