public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: online browsable ebuilds by arch?
Date: Tue, 31 Mar 2015 00:01:28 +0100	[thread overview]
Message-ID: <20150331000128.1ff751bd@digimed.co.uk> (raw)
In-Reply-To: <loom.20150330T230033-911@post.gmane.org>

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

On Mon, 30 Mar 2015 21:05:46 +0000 (UTC), James wrote:

> > That's the main portage tree, the name is a misnomer. Although called
> > gentoo-x86, it is really just portage, which does not have specific
> > ebuilds for different architectures. Architecture suitability is
> > governed by the KEYWORDS variable inside the ebuild.  
> 
> 
> Yea, I get that. But I want it 100% filtered by arch.
> 
> So if I'm looking for ppc (a gentoo supported arch) I have an online
> portage tree for viewing; so that ALL packages listed, are available
> for a specific arch. There are many amd64/x86/intel only packages
> that are not yet ported to a specific arch.  So how do I filter
> the above repo to ensure I only see those packages available
> for other architectures?

It's not quite what you are asking for, but packages.g.o lets you
filter by arch, and view the contents of ebuilds.


-- 
Neil Bothwick

I've got a Mickey Mouse PC with a Goofy operating system.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2015-03-30 23:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30 15:49 [gentoo-user] online browsable ebuilds by arch? James
2015-03-30 19:39 ` Neil Bothwick
2015-03-30 21:05   ` [gentoo-user] " James
2015-03-30 23:01     ` Neil Bothwick [this message]
2015-03-31  5:21       ` James
2015-03-31  7:31         ` Neil Bothwick
2015-03-31 20:02           ` Bob Wya

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=20150331000128.1ff751bd@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --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