public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] About current ppc/ppc64 status
Date: Fri, 25 Jul 2014 15:57:20 -0400	[thread overview]
Message-ID: <53D2B6A0.4070009@gentoo.org> (raw)
In-Reply-To: <1406317833.20388.24.camel@gentoo.org>

On 07/25/14 15:50, Pacho Ramos wrote:
> El vie, 25-07-2014 a las 15:38 -0400, Anthony G. Basile escribió:
>> On 07/25/14 15:28, Pacho Ramos wrote:
>>> That is the reason for me thinking that maybe the way to go would be to
>>> do the opposite -> keep only base-system and a few others stable and
>>> drop stable for most of the rest. This big effort could be accomplished
>>> in a week by other developers willing to help (like me) and would solve
>>> the issue for the long term. I guess that is what HPPA team did in the
>>> past and I think it's working pretty well for them (in summary, have a
>>> stable tree they are able to keep stable). That will also help people in
>>> ppc* teams to know that the remaining stabilization bugs, apart of being
>>> much less, are important enough to deserve rapid attention, as opposed
>>> to current situation that will have some important bugs mixed with tons
>>> of stabilization requests of apps that got ppc stable keywords years ago
>>> and are currently no so important.
>>>
>> Yes, please let's just do base system stable.  I've been randomly taking
>> care of ppc but nothing systematic.  Its pretty spotty.  But at the same
>> time I don't like the idea of just loosing all the stabilization effort
>> on the base system, so that might work best. Something to think about
>> for mips too.
>>
>>
> Nice, one think we would need to discuss is what do we consider base
> system :/
>
> I guess packages maintained by base-system, toolchain and... xorg-server
> and co... what more
>
> Not sure if we could have a list of current stable tree for ppc*, once
> do we have that list, ppc* teams can drop from that list what they want
> and we get a new list that will be the final result. What do you think
> about that?
>
>

At the very least, its what's needed to build the stages with catalyst.  
I would think we should start with base/packages, but I don't want to 
limit it to just those because I at least need a more for building and 
maintaining.  Where should we start to compile such a list?

-- 
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail    : blueness@gentoo.org
GnuPG FP  : 1FED FAD9 D82C 52A5 3BAB  DC79 9384 FA6E F52D 4BBA
GnuPG ID  : F52D4BBA



  reply	other threads:[~2014-07-25 19:56 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-25 19:28 [gentoo-dev] About current ppc/ppc64 status Pacho Ramos
2014-07-25 19:38 ` Anthony G. Basile
2014-07-25 19:50   ` Pacho Ramos
2014-07-25 19:57     ` Anthony G. Basile [this message]
2014-07-25 20:07       ` William Hubbs
2014-07-26  8:36         ` Pacho Ramos
2014-07-26  8:44           ` Pacho Ramos
2014-07-26  9:09             ` Johannes Huber
2014-07-26 11:57               ` Manuel Rüger
2014-07-26 11:59                 ` Pacho Ramos
2014-07-26 12:16                   ` Anthony G. Basile
2014-07-26 10:22             ` Anthony G. Basile
2014-07-26 11:36               ` Pacho Ramos
2014-07-26 11:47                 ` Anthony G. Basile
2014-07-26 11:56                   ` Pacho Ramos
2014-07-26 12:23                     ` Rich Freeman
2014-07-26 13:25                       ` Pacho Ramos
2014-07-26 12:55                     ` Andreas K. Huettel
2014-07-26 13:28                       ` Pacho Ramos
2014-07-26 13:37                         ` Anthony G. Basile
2014-07-26 13:44                           ` Pacho Ramos
2014-07-26 20:29                             ` Anthony G. Basile
2014-07-26 22:01                               ` Pacho Ramos
2014-07-29 14:30                                 ` Anthony G. Basile
2014-07-30  2:16                               ` Jack Morgan
2014-07-30 10:26                                 ` Anthony G. Basile
2014-07-30 21:18                                   ` Joseph Jezak
2014-07-30 23:44                                     ` Anthony G. Basile
2014-07-31  0:21                                       ` Jack Morgan
2014-07-26 11:44               ` Samuli Suominen
2014-07-26 12:53             ` Andreas K. Huettel
2014-07-26 15:39             ` William Hubbs
2014-07-26 16:20               ` William Hubbs
2014-07-26 16:31                 ` Andreas K. Huettel
2014-07-26 17:19                   ` William Hubbs
2014-07-26 17:33                     ` [gentoo-dev] " Michael Palimaka
2014-08-01  8:52                       ` Raúl Porcel
2014-08-01  9:35                         ` Joshua Kinard
2014-08-02  8:59                           ` Joshua Kinard
2014-08-01 10:28                         ` Duncan
2014-07-26 16:40                 ` Michael Palimaka

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=53D2B6A0.4070009@gentoo.org \
    --to=blueness@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