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] helixplayer-bin question, and wget with https proxy
Date: Tue, 18 May 2004 18:16:41 +0200	[thread overview]
Message-ID: <20040518181641.78cd94db@sven.genone.homeip.net> (raw)
In-Reply-To: <20040518155033.GT8712@zk3.dec.com>

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

On 05/18/04  Joel Martin wrote:

> Options:
> - Just remove the ebuilds with fetch restrictions.
> - Make the 0.3.0.123 stable right now (probably the wrong route)
> - Make the ones with fetch restrictions -x86, so that the user has to
>   force it. This is the one I'm leaning towards, because this way,
>   enterprising users have the ebuild to use the fetch restricted
>   helixplayer, but most users just get the alpha version 0.3.0.123 and
>   don't have to worry about fetch restrictions.

If the 123 and 124 versions are identical otherwise I'd go for option
one or package.mask'ing 124, I don't like using KEYWORDS for such stuff
(as -arch means: "doesn't work", not: "is inconvienient"). package.mask
has the advantage that you can provide a comment to explain why you
masked it.

Marius

-- 
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: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-05-18 16:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-18 14:13 [gentoo-dev] libc.so.6 error Ajai Khattri
2004-05-18 15:50 ` [gentoo-dev] helixplayer-bin question, and wget with https proxy Joel Martin
2004-05-18 16:16   ` Marius Mauch [this message]
2004-05-18 19:56 ` [gentoo-dev] libc.so.6 error Stefan Jones

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=20040518181641.78cd94db@sven.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