[gentoo-dev] Re: Bug #565566: Why is it still not fixed?

2016-02-23 Thread Duncan
Kent Fredric posted on Wed, 24 Feb 2016 18:49:06 +1300 as excerpted: > But I'm sure at least one person out there has probably gone looking for > a changelog to see when something got stabilized/keyworded. In particular, I tend to be looking for this level of "introduced-on ymd to the kde

Re: [gentoo-dev] Re: Bug #565566: Why is it still not fixed?

2016-02-23 Thread Kent Fredric
On 24 February 2016 at 17:24, Duncan <1i5t5.dun...@cox.net> wrote: > Particularly when the basic changelog information is there, it's simply > quibbling about chronological or reverse-chronological order we're doing > now, and people who /really/ care about it by rights should be going > straight

[gentoo-dev] Re: Bug #565566: Why is it still not fixed?

2016-02-23 Thread Duncan
Vadim A. Misbakh-Soloviov posted on Wed, 24 Feb 2016 10:38:55 +0600 as excerpted: >> Is this actually true? For the typical use case of daily or close to >> daily updates I'd think that git would be much more efficient. > As there were noticed multiple times on the list already, this should >

Re: [gentoo-dev] Re: Bug #565566: Why is it still not fixed?

2016-02-23 Thread Vadim A. Misbakh-Soloviov
> Is this actually true? For the typical use case of daily or close to > daily updates I'd think that git would be much more efficient. As there were noticed multiple times on the list already, this should not ever happen, at least, until git will support resumable fetches/clones/whatever.

[gentoo-dev] Re: Bug #565566: Why is it still not fixed?

2016-02-23 Thread Duncan
Rich Freeman posted on Tue, 23 Feb 2016 21:53:45 -0500 as excerpted: > In the degenerate case where nothing has changed, an rsync still needs > to walk the full tree and send a file list, while git just sends a > commit ID and terminates. Technicality: While I believe you're correct for pure

Re: [gentoo-dev] Re: Bug #565566: Why is it still not fixed?

2016-02-23 Thread Rich Freeman
On Tue, Feb 23, 2016 at 7:50 PM, Kristian Fiskerstrand wrote: > > On 02/24/2016 01:33 AM, Duncan wrote: >> >> IMO, what's actually happening here is the slow deprecation of >> rsync mirrors in favor of git. I doubt they'd be created at all >> if gentoo were > > I don't agree to

Re: [gentoo-dev] Re: Bug #565566: Why is it still not fixed?

2016-02-23 Thread Rich Freeman
On Tue, Feb 23, 2016 at 7:33 PM, Duncan <1i5t5.dun...@cox.net> wrote: > > Which means it's the tools that expect reverse-chronological order that > must change. Either that, or people /that/ concerned about the > changelogs can simply switch to the git repos and use the existing git > tools to

Re: [gentoo-dev] bidi / fribidi useflag harmonization

2016-02-23 Thread Daniel Campbell
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 02/22/2016 02:09 AM, Patrick Lauer wrote: > We have two useflags expressing the same thing: bidi and fribidi. > > I suggest collapsing it into one useflag, and to make it a global > useflag. > > Affected packages: > >

Re: [gentoo-dev] Re: Bug #565566: Why is it still not fixed?

2016-02-23 Thread Kristian Fiskerstrand
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 02/24/2016 01:33 AM, Duncan wrote: > > IMO, what's actually happening here is the slow deprecation of > rsync mirrors in favor of git. I doubt they'd be created at all > if gentoo were I don't agree to this at all. For one thing git is very

[gentoo-dev] Re: Bug #565566: Why is it still not fixed?

2016-02-23 Thread Duncan
Patrick Lauer posted on Tue, 23 Feb 2016 22:53:32 +0100 as excerpted: > On 02/23/2016 07:07 PM, Alec Warner wrote: >> On Tue, Feb 23, 2016 at 9:14 AM, Patrick Lauer > > wrote: >> >> See https://bugs.gentoo.org/show_bug.cgi?id=565566 >> >>

Re: [gentoo-dev] Bug #565566: Why is it still not fixed?

2016-02-23 Thread Patrick Lauer
On 02/23/2016 07:07 PM, Alec Warner wrote: > On Tue, Feb 23, 2016 at 9:14 AM, Patrick Lauer > wrote: > > See https://bugs.gentoo.org/show_bug.cgi?id=565566 > > Since we have ChangeLogs again (November) they've been in backwards > order.

Re: [gentoo-dev] Bug #565566: Why is it still not fixed?

2016-02-23 Thread Alexis Ballier
On Tue, 23 Feb 2016 18:14:36 +0100 Patrick Lauer wrote: > See https://bugs.gentoo.org/show_bug.cgi?id=565566 > > Since we have ChangeLogs again (November) they've been in backwards > order. Which is not really good - it breaks tools (like emerge > --changelog) and makes it

Re: [gentoo-portage-dev] [PATCH] doebuild: abort for missing DIST digests

2016-02-23 Thread Brian Dolbec
On Tue, 23 Feb 2016 09:42:51 -0800 Zac Medico wrote: > Fix the ebuild(1) command to abort when DIST digests are missing, > so behavior is consistent with emerge. Do not abort when generating > a manifest (including when "digest" is in FEATURES), or when the > ebuild

[gentoo-portage-dev] [PATCH] doebuild: abort for missing DIST digests

2016-02-23 Thread Zac Medico
Fix the ebuild(1) command to abort when DIST digests are missing, so behavior is consistent with emerge. Do not abort when generating a manifest (including when "digest" is in FEATURES), or when the ebuild --skip-manifest option is used (these cases are handled outside of the doebuild function).

[gentoo-dev] Bug #565566: Why is it still not fixed?

2016-02-23 Thread Patrick Lauer
See https://bugs.gentoo.org/show_bug.cgi?id=565566 Since we have ChangeLogs again (November) they've been in backwards order. Which is not really good - it breaks tools (like emerge --changelog) and makes it harder to read for humans. As a bonus it's inconsistent because the old Changelog-2015

Re: [gentoo-dev] games.eclass policy

2016-02-23 Thread Vadim A. Misbakh-Soloviov
17.02.2016 21:32, Denis Dupeyron пишет: > On Wed, Feb 17, 2016 at 12:39 AM, Michał Górny wrote: > >> developers who did what they cared about and ignored everything and >> everyone else. >> > I don't know if I'm an exception to the rule, but I've always had fruitful >