public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Beso <givemesugarr@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: kde4, xorg, xf86-video-ati/radeon, and multi-panel display
Date: Sun, 23 Nov 2008 11:56:36 +0000	[thread overview]
Message-ID: <d257c3560811230356l13b249cfm8fd974dfc493b094@mail.gmail.com> (raw)
In-Reply-To: <pan.2008.11.23.11.39.34@cox.net>

2008/11/23 Duncan <1i5t5.duncan@cox.net>:
> Beso <givemesugarr@gmail.com> posted
> d257c3560811230303g48cd3972mab017762f95ee51@mail.gmail.com, excerpted
> below, on  Sun, 23 Nov 2008 11:03:36 +0000:
>
>> non ability for binpkg of paludis
>
> I've wondered about that.  binpkg is a seriously used feature here, even
> with just a single machine (well two now, but the second isn't running
> Gentoo yet), as it plays a big part in both my backup and troubleshooting
> routines.  I've long argued that FEATURES=buildpkg is one of the most
> undersold great features of portage, particularly since at its core it's
> a simple bzip2ed tarball with a bit of extra data tacked on the end, so
> it's easily worked with using virtually any *ix based archiver tools you
> might prefer for exploration and/or extraction, emergency or otherwise.
>
> But as I've always said, he who writes the code, calls the shots, and
> those writing the paludis code obviously don't consider binpkgs that
> important, so the feature has yet to be implemented.
>
> Of course that has nothing to do with why I won't let it touch my system,
> despite my extremely high respect for the devs' technical abilities.  I'm
> trying my best to stay nice here...
>
well, i don't want to start up a flame, but with portage i had very often issues
with having the deps discovered in the right way. of course when the system
is up and running this isn't so much of a trouble, but when you set it
up or when
you do an upgrade that still has quite some deps discovered then the problem
is to be seen. of course the hour it takes paludis to build a dual core with 4
compilation jobs is to be considered. portage only takes less than 30secs to
upgrade. well, anyway, i always find good having at least 2 working package
installers on my system so that i can see out bugs for one or the
other. also not
using the binpkg feature if one of then fails then the problem is quite big.

-- 
dott. ing. beso



  reply	other threads:[~2008-11-23 11:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-23  7:23 [gentoo-amd64] kde4, xorg, xf86-video-ati/radeon, and multi-panel display Duncan
2008-11-23 10:20 ` [gentoo-amd64] " ABCD
2008-11-23 11:00   ` ABCD
2008-11-23 11:03   ` Beso
2008-11-23 11:39     ` Duncan
2008-11-23 11:56       ` Beso [this message]
2008-11-23 13:10         ` Duncan
2008-11-23 11:06 ` Duncan
2008-11-23 11:38   ` Beso
2008-11-23 12:33     ` Duncan
2008-11-23 11:24 ` [gentoo-amd64] " Beso
2008-11-23 12:08   ` [gentoo-amd64] " Duncan

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=d257c3560811230356l13b249cfm8fd974dfc493b094@mail.gmail.com \
    --to=givemesugarr@gmail.com \
    --cc=gentoo-amd64@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