public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marius Mauch <genone@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Why Glep42 news can't be used yet
Date: Sun, 6 May 2007 16:49:37 +0200	[thread overview]
Message-ID: <20070506164937.416f431b@sheridan.genone.homeip.net> (raw)
In-Reply-To: <200705061600.29658.peper@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2226 bytes --]

On Sun, 6 May 2007 16:00:29 +0200
Piotr Jaroszyński <peper@gentoo.org> wrote:

> On Sunday 06 of May 2007 15:40:23 Marius Mauch wrote:
> > Apparently the `eselect news` module (which is the suggested
> > default news reader) requires paludis to be installed and
> > configured, a quick test resulted in errors when trying with
> > a) paludis not installed
> > b) paludis installed but not configured
> > and the code doesn't seem to have any support for portage at this
> > time (checked version was eselect-1.0.9).
> Well it's part of Paludis... 
> Tbh, I expected a little more from portage support for news items
> than pointing to eselect module made for paludis.

Well, the default is specified by the glep and I expected it to be part
of eselect (which is why I didn't check at first what package installed
it), especially given that several eselect authors are also paludis
devs.
And shipping another module (there appears to be one in svn[1]) for
portage would mean either to use a different name (which sucks
UI-wise IMHO) or make paludis and portage block each other (which I
think everyone will agree is the worst solution).

But as long as this problem persists we cannot issue more news items
for the gentoo-x86 repository. Now what solutions are there:

a) add portage support to the paludis news.eselect and move it into the
main eselect package (or make a standalone package)
b) let portage install its own module (sucks for reasons given above)
c) ignore the glep and write a non-eselect reader app to be
installed/depended on by portage and used by portage whenever a default
is required

Out of those a) is IMO preferrably unless someone can come up with a
better solution.

Btw, if you knew about this issue before (that's how your statement
above sounds to me) then I'm somewhat irritated that you didn't consider
it worth mentioning when you first brought the topic up.

Marius

[1]
http://sources.gentoo.org/viewcvs.py/portage/private/antarus/glep42/eselect/

-- 
Public Key at http://www.genone.de/info/gpg-key.pub

In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothing, but you could see a bit better.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-05-06 14:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-06 13:40 [gentoo-dev] Why Glep42 news can't be used yet Marius Mauch
2007-05-06 13:47 ` Marius Mauch
2007-05-06 14:00 ` Piotr Jaroszyński
2007-05-06 14:49   ` Marius Mauch [this message]
2007-05-06 15:28     ` Piotr Jaroszyński
2007-05-06 15:44 ` Ciaran McCreesh
2007-05-06 16:30   ` Marius Mauch

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=20070506164937.416f431b@sheridan.genone.homeip.net \
    --to=genone@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