On Oct 19 20:13, Achim Gratz wrote:
> Yaakov Selkowitz writes:
> > Switchable versioning schemes means that code has to be multiplied in
> > both setup and upset, which is just asking for problems. There needs to
> > be one single versioning scheme, period, and using RPM's makes sense.
>
> You
On Oct 19 19:21, Achim Gratz wrote:
> Corinna Vinschen writes:
> > I agree. Actually, considering that the info files are stored in just a
> > single well-known directory, /usr/share/info(*), and further considering
> > that updated files are rewritten when overwritten, shouldn't it be entirely
>
Jari, ping?
On Oct 19 17:54, Marco Atzeri wrote:
> On 19/10/2015 17:45, Corinna Vinschen wrote:
> >On Sep 26 11:43, Marco Atzeri wrote:
> >>Jari,
> >>any specific reason why there is only a 64 bit version ?
> >>
> >>As it seems just a python script, it should work on both arch correct ?
> >
>
On Oct 20 12:03, Yaakov Selkowitz wrote:
> On Tue, 2015-10-20 at 17:50 +0200, Corinna Vinschen wrote:
> > > Adding epoch parsing would be additional work. I'm not sure how much
> > > value
> > > that would have since (a) we are effectively limited to 2 package
> > > versions,
> > > and (b) we
Ken Brown writes:
> On 5/25/2015 2:45 PM, Ken Brown wrote:
> It doesn't look like anything is going to change in the near
> future. According to the bug report I cited, Biber runs slower by a
> factor of 20 with version 1.18 of Unicode::Normalize than with version
> 1.17. I don't think that's
Jon Turney writes:
>> All of this is already existing in Cygwin,
>
> It exists in upset, but not in way that anyone can rely on working the
> way they think it's going to, since the implementation is bewildering
> and undocumented.
I was talking about the sort of version numbering schemes that
On Oct 20 14:33, Jon Turney wrote:
> On 20/10/2015 11:27, Corinna Vinschen wrote:
> >On Oct 19 20:13, Achim Gratz wrote:
> >>Yaakov Selkowitz writes:
> >>>Switchable versioning schemes means that code has to be multiplied in
> >>>both setup and upset, which is just asking for problems. There
On Tue, 2015-10-20 at 09:25 -0400, Remik Ziemlinski wrote:
> Name: Remik Ziemlinski
> Package: nccmp
Key added, you may proceed with uploading.
--
Yaakov
On Tue, 2015-10-20 at 17:50 +0200, Corinna Vinschen wrote:
> > Adding epoch parsing would be additional work. I'm not sure how much value
> > that would have since (a) we are effectively limited to 2 package versions,
> > and (b) we can force a given ordering using setup.hint
>
> Yaakov thinks
Yaakov Selkowitz writes:
> In short, xdelta was updated from 1.x to 3.x, then it was realized that
> both were needed, and so xdelta was reverted to 1.x and xdelta3 was
> created. Instead of saying "oh btw you need to revert xdelta to 1.x
> yourself" (which is all we could do currently), the
On Tue, 2015-10-20 at 21:53 +0200, Achim Gratz wrote:
> Yaakov Selkowitz writes:
> > In short, xdelta was updated from 1.x to 3.x, then it was realized that
> > both were needed, and so xdelta was reverted to 1.x and xdelta3 was
> > created. Instead of saying "oh btw you need to revert xdelta to
On 10/20/2015 3:31 PM, Achim Gratz wrote:
Ken Brown writes:
On 5/25/2015 2:45 PM, Ken Brown wrote:
It doesn't look like anything is going to change in the near
future. According to the bug report I cited, Biber runs slower by a
factor of 20 with version 1.18 of Unicode::Normalize than with
On 20/10/2015 11:27, Corinna Vinschen wrote:
On Oct 19 20:13, Achim Gratz wrote:
Yaakov Selkowitz writes:
Switchable versioning schemes means that code has to be multiplied in
both setup and upset, which is just asking for problems. There needs to
be one single versioning scheme, period, and
On 19/10/2015 18:19, Achim Gratz wrote:
Corinna Vinschen writes:
I don't really want to spend effort on unravelling the complexities of the
sorting that upset does, since I don't think it's worth keeping, and we
should switch to a scheme which can be described in a paragraph,
e.g. the scheme
14 matches
Mail list logo
