> > Proposal No 2:
> > * Leave profiles.desc unmodified
> > * Introduce a new file arch.desc, which contains the "stability
> > status" of an
> > arch;
> >
> > Syntax: 2 columns,
> > # arch status
> > amd64 stable
> > mipstesting
> > sh unstable
> >
> > The meaning of the
Am Montag, 30. Januar 2017, 09:29:06 CET schrieb Kent Fredric:
> ---
>amd64 keywords=strict checkdeps=stable enforcedeps=stable
>mips keywords=mixed checkdeps=stable enforcedeps=dev
>m68k keywords=mixed checkdeps=expenforcedeps=exp
> ---
The problem with this is that (already
On Sun, 29 Jan 2017 14:08:05 -0500
james wrote:
> I do
> not have access to Kent's posting so perhaps a reference to Kent's ideas?
Happened on IRC, not on any ML ( though I copied a basic copy of it in another
thread )
But I'm not going to reiterate it here due to its chances of introducing
On 01/29/2017 10:06 AM, Andreas K. Huettel wrote:
So I've been talking to kent\n and the conclusion is that our ideas basically
do and achieve the same, with a slightly different approach. (I still like
mine better though. :)
However one valid point that came up in discussions is - whether an ar
On Sun, 29 Jan 2017 18:20:34 +0200
Mart Raudsepp wrote:
> Might want a "broken" (with maybe a better name) for some of these. I
> bet the ~arch of some of these is broken too, and no-one to respond to
> keyword requests, just happens when it happens.
> arm64 and mips are in that state too until w
On Sun, 29 Jan 2017 18:20:34 +0200
Mart Raudsepp wrote:
> Maybe declare from the start that any extra columns should be silently
> ignored in implementations from start, as to be able to safely add more
> columns in the future without breaking backwards compatibility.
Maybe not silently, maybe j
Ühel kenal päeval, P, 29.01.2017 kell 16:06, kirjutas Andreas K.
Huettel:
> However one valid point that came up in discussions is - whether an
> arch
> supports stable keywords is a per-arch setting, not a per-profile
> setting. So
> we can actually make things much easier (and the transition sa
So I've been talking to kent\n and the conclusion is that our ideas basically
do and achieve the same, with a slightly different approach. (I still like
mine better though. :)
However one valid point that came up in discussions is - whether an arch
supports stable keywords is a per-arch setting
