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] webkit-gtk build failure and masking confusion
Date: Mon, 19 Feb 2018 18:59:57 +0000	[thread overview]
Message-ID: <20180219185957.7226eaa6@digimed.co.uk> (raw)
In-Reply-To: <3698f8fd-6b1a-c2ff-d204-1f41787b6027@sys-concept.com>

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

On Mon, 19 Feb 2018 11:05:37 -0700, thelma@sys-concept.com wrote:

> It is a good point. Why Gentoo developers marked or allow to mark
> gnucash-2.7 branch stable in portage when the developers
> https://www.gnucash.org/download.phtml did not mark it STABLE

The key phrase there is "stable in portage". Not whether it is suitable
or not for any particular use. If the ebuild is considered stable, it
should be marked as such.


-- 
Neil Bothwick

furbling, v.:
	Having to wander through a maze of ropes at an airport or bank
	even when you are the only person in line.
		-- Rich Hall, "Sniglets"

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

  reply	other threads:[~2018-02-19 19:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-17 20:23 [gentoo-user] webkit-gtk build failure and masking confusion John Blinka
2018-02-17 20:38 ` Neil Bothwick
2018-02-17 23:20   ` John Blinka
2018-02-18  2:14     ` Neil Bothwick
2018-02-18  2:30       ` allan gottlieb
2018-02-18  4:07       ` Jack
2018-02-18  9:52         ` Neil Bothwick
2018-02-19 16:52       ` Peter Humphrey
2018-02-18  1:09 ` allan gottlieb
2018-02-18  8:51   ` Mick
2018-02-18  9:49     ` Neil Bothwick
2018-02-18 15:41       ` allan gottlieb
2018-02-18 15:39     ` allan gottlieb
2018-02-19  0:50       ` John Blinka
2018-02-19  1:42         ` allan gottlieb
2018-02-19 18:05         ` thelma
2018-02-19 18:59           ` Neil Bothwick [this message]
2018-02-19 19:40             ` allan gottlieb

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=20180219185957.7226eaa6@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