Gentoo Archives: gentoo-portage-dev

From: Brian Dolbec <dolsen@g.o>
To: gentoo-portage-dev@l.g.o
Subject: Re: [gentoo-portage-dev] Re: [PATCH] man/ebuild.5: Update description of =* operator.
Date: Wed, 23 Sep 2015 05:47:13
Message-Id: 20150922224616.64f8273b.dolsen@gentoo.org
In Reply to: [gentoo-portage-dev] Re: [PATCH] man/ebuild.5: Update description of =* operator. by Duncan <1i5t5.duncan@cox.net>
1 On Wed, 23 Sep 2015 05:04:57 +0000 (UTC)
2 Duncan <1i5t5.duncan@×××.net> wrote:
3
4 > Brian Dolbec posted on Tue, 22 Sep 2015 08:09:06 -0700 as excerpted:
5 >
6 > > On Tue, 22 Sep 2015 16:45:38 +0200 Alexander Berntsen
7 > > <bernalex@g.o> wrote:
8 > >
9 > >> On 22/09/15 16:27, Brian Dolbec wrote:
10 > >> > But, I wonder if the change had a bug side effect...causing him
11 > >> > the grief
12 > >> It appears the "problem" is that he can't exploit an old bug. So
13 > >> it's actually the opposite.
14 > >>
15 > > hey, I'm still waking up ;) I went over the previous emails/patch.
16 > > Yeah, I see it clearly now. He was splitting the date suffix,
17 > > which the whole date is considered as one boundary zone.
18 >
19 > Second hand as I don't do IRC (tho the date string example was
20 > specifically mentioned on the big dev thread a couple times, and I
21 > was as a result surprised to see the "bug fix" here without so much
22 > as a mention that if the date string thing worked it was only by
23 > accident, as it was always exploiting a bug...)
24 >
25 > But as a workaround, has anyone suggested the obvious... 2015.0922 ?
26 >
27 > I find 2015.0922 visually easier to parse than 20150922, in any case,
28 > and in fact routinely do break it down into four-digit substrings
29 > here, as extensions for dated backups of various critical config
30 > files, etc.
31 >
32
33
34 No, as portage developers we were too busy looking over our shoulders
35 watching out for the pitch-fork and torches wielding angry mob, because
36 we fixed a bug... ;) which turns out only seems to have affected one
37 developer/user and 2 ebuilds. But the thought did cross my mind
38 earlier today. And seeing it here now, yes, I agree it does look
39 better and easier to read. But as a long used form, the old/existing
40 method will likely be hard to to get devs to convert to the split form.
41 --
42 Brian Dolbec <dolsen>