On 2/26/2018 12:45 PM, Jon Turney wrote:
>
> You might find the code in [1] a good starting point for an alternate
> implementation, which doesn't require renaming the executable.
>
> [1] https://cygwin.com/ml/cygwin-apps/2011-04/msg00054.html
Chris Faylor:
>>
>> Sounds wonderful but couldn't
cyg Simple writes:
> That point was already addressed by Jon and my retort was that the issue
> could be resolved by supplying a symlink for the name without the version.
You still failed to provide an evidence of the benefits outweighing the
drawbacks. Also, I'm neither buying your argument
On 2/27/2018 10:32 AM, Marco Atzeri wrote:
> On 27/02/2018 15:32, cyg Simple wrote:
>> On 2/26/2018 12:45 PM, Jon Turney wrote:
>
>> I'll take a look at your reference and provide comment under a different
>> response. However, not versioning the file isn't something I am
>> promoting as I am of
On 27/02/2018 15:32, cyg Simple wrote:
On 2/26/2018 12:45 PM, Jon Turney wrote:
I'll take a look at your reference and provide comment under a different
response. However, not versioning the file isn't something I am
promoting as I am of the belief that the delivered executable should
have a
On 2/26/2018 12:45 PM, Jon Turney wrote:
> On 26/02/2018 17:10, cyg Simple wrote:
>> On 2/26/2018 9:02 AM, Jon Turney wrote:
>>> This allows setup.ini to require a certain setup version, rather than
>>> advise
>>> a newer version when one is available.
>>>
>>> Unfortunately, versions of setup
On 26/02/2018 17:10, cyg Simple wrote:
On 2/26/2018 9:02 AM, Jon Turney wrote:
This allows setup.ini to require a certain setup version, rather than advise
a newer version when one is available.
Unfortunately, versions of setup prior to this one don't implement this, but
at least we have this
On 2/26/2018 9:02 AM, Jon Turney wrote:
> This allows setup.ini to require a certain setup version, rather than advise
> a newer version when one is available.
>
> Unfortunately, versions of setup prior to this one don't implement this, but
> at least we have this going forward.
>
> When we want
This allows setup.ini to require a certain setup version, rather than advise
a newer version when one is available.
Unfortunately, versions of setup prior to this one don't implement this, but
at least we have this going forward.
When we want to start using this, we can break backwards
