public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ferris McCormick <fmccor@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] xorg-x11-7 emerge blocks
Date: Mon, 24 Oct 2005 23:45:36 +0000 (UTC)	[thread overview]
Message-ID: <Pine.LNX.4.64.0510242326330.10291@terciopelo.krait.us> (raw)
In-Reply-To: <200510250045.39187.danarmak@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 25 Oct 2005, Dan Armak wrote:

> On Monday 24 October 2005 19:24, Ferris McCormick wrote:
>> On Mon, 2005-10-24 at 18:48 +0200, Dan Armak wrote:
>>> Don't post such questions here. Go to the gentoo-user mailing list, the
>>> forums, or irc. This list is for discussion of Gentoo development.
>>
>> Actually, this is a discussion of X-modular, and up to now, all
>> X-modular posts have come here (it is very much a -dev issue; the
>> X-modular suite is masked, unless something has changed quite recently.)
>
> It was a matter of misunderstanding emerge output (block by <xorg-x11-7, and
> the OP apparently missed the <). Thus nothing to do with the modular X. It
> was also crossposted to gentoo-user. IMHO mostly any question about using
> portage correctly, which is suitable to gentoo-user, is not suitable to
> gentoo-dev.
>
Well, maybe so.  However that missing '<' is kind of important, and when 
playing with X-modular, the portage output really looks like the modular 
packages are blocking the non-existent xorg-x11-7.  It's not a "matter of 
using portage correctly" because portage is misreporting the (phantom) 
problem.

As I recall, it looks like this (for example):
x11-base/xorg-server-xxx [B x11-base/xorg-x11-7]
which without that little '<' is, shall we say, wrong.  Since (so far as I 
know) it arises only in the X-modular context, this is the right place for 
the question.  (With '<' it's true but irrelevant, but portage is being 
misled into believing xorg-x11 is required.  R. Hill addressed that issue in
another post.)

Or maybe it arises elsewhere too?

> Maybe I was too harsh in the tone of my reply. If so I 
apologize.
>> -- 
> Dan Armak
> Gentoo Linux developer (KDE)
> Public GPG key: http://dev.gentoo.org/~danarmak/danarmak-gpg-public.key
> Fingerprint: DD70 DBF9 E3D4 6CB9 2FDD  0069 508D 9143 8D5F 8951
>

Regards,
Ferris

- --
Ferris McCormick (P44646, MI) <fmccor@gentoo.org>
Developer, Gentoo Linux (sparc, devrel)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDXXIjQa6M3+I///cRAlXxAJ9wGluXrvSQ9KOQkKhSAwpOVPMENwCfXVRi
KjILUCOMih2TH0IG1YQdM8k=
=11KQ
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-10-24 23:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-24 14:18 [gentoo-dev] xorg-x11-7 emerge blocks Massimiliano Bellomo
2005-10-24 16:48 ` Dan Armak
2005-10-24 17:24   ` Ferris McCormick
2005-10-24 22:45     ` Dan Armak
2005-10-24 23:45       ` Ferris McCormick [this message]
2005-10-25 12:46         ` Dan Armak
2005-10-24 21:06 ` [gentoo-dev] " R Hill
2005-10-25 12:56 ` [gentoo-dev] " Norguhtar

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=Pine.LNX.4.64.0510242326330.10291@terciopelo.krait.us \
    --to=fmccor@gentoo.org \
    --cc=gentoo-dev@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