On 21/06/2016 13:03, Corinna Vinschen wrote:
On Jun 20 16:28, Jon Turney wrote:
[...]
* 'curr', 'prev' and 'test' don't make sense on a per-version basis. So I
suggest a separate file for these version overrides (versions.hint?)
Ideally we wouldn't need something like "prev" at all since the
Eric Blake writes:
> Except when upstream version numbers go backwards. We'd have to adopt
> something like Fedora's "epoch" numbering if we want our version numbers
> to always be increasing (by bumping the epoch any time upstream versions
> go backwards).
Oh please not. I've looked into this a
On 21/06/2016 16:28, Corinna Vinschen wrote:
On Jun 21 15:49, Marco Atzeri wrote:
On 21/06/2016 14:03, Corinna Vinschen wrote:
On Jun 20 16:28, Jon Turney wrote:
Ideally we wouldn't need something like "prev" at all since the version
number itself is sufficient to specify what's curr an
On Jun 21 15:49, Marco Atzeri wrote:
>
> On 21/06/2016 14:03, Corinna Vinschen wrote:
> > On Jun 20 16:28, Jon Turney wrote:
> > >
> > > Currently, the setup.hint file is shared between all versions.
> > >
> > > This means that manual intervention (by the package maintainer, or on
> > > sourcewa
On Jun 21 08:08, Eric Blake wrote:
> On 06/21/2016 06:03 AM, Corinna Vinschen wrote:
>
> >> * 'curr', 'prev' and 'test' don't make sense on a per-version basis. So I
> >> suggest a separate file for these version overrides (versions.hint?)
> >
> > Ideally we wouldn't need something like "prev" a
On 06/21/2016 06:03 AM, Corinna Vinschen wrote:
>> * 'curr', 'prev' and 'test' don't make sense on a per-version basis. So I
>> suggest a separate file for these version overrides (versions.hint?)
>
> Ideally we wouldn't need something like "prev" at all since the version
> number itself is suff
On 21/06/2016 14:03, Corinna Vinschen wrote:
On Jun 20 16:28, Jon Turney wrote:
Currently, the setup.hint file is shared between all versions.
This means that manual intervention (by the package maintainer, or on
sourceware) is needed when versions have different dependencies.
To automate th
On Jun 21 09:01, Thomas Wolff wrote:
> I had recently reported that an old network installation problem, that had
> been resolved meanwhile, reappeared:
> https://cygwin.com/ml/cygwin-apps/2015-12/msg00012.html
>
> As an additional observation, on the same machine, there is also a virtual
> machin
On Jun 20 16:28, Jon Turney wrote:
>
> Currently, the setup.hint file is shared between all versions.
>
> This means that manual intervention (by the package maintainer, or on
> sourceware) is needed when versions have different dependencies.
>
> To automate this problem out of existence, I sugg
I had recently reported that an old network installation problem, that
had been resolved meanwhile, reappeared:
https://cygwin.com/ml/cygwin-apps/2015-12/msg00012.html
As an additional observation, on the same machine, there is also a
virtual machine running Windows XP. From that, I can use set
10 matches
Mail list logo
