Hi folks,
I recently ran into a problem where I needed to update my copy of upset
to handle the new message mechanism in setup. It appears the upset
sources are now locked away, inaccessible to mere mortals such as
myself. Is there a particular reason these have been locked up?
Looking at m
On Wed, Feb 17, 2010 at 06:01:29AM -0700, Eric Blake wrote:
>According to Christopher Faylor on 2/16/2010 3:29 PM:
>> Actually:
>>
>> 6c6
>> < requires: bash cygwin
>> ---
>> > requires: bash cygwin libgcc1 coreutils
>
>And you should be omitting the 'requires: cygwin' dependency as redund
According to Pierre A. Humblet on 2/17/2010 6:05 AM:
> At 08:01 AM 2/17/2010, Eric Blake wrote:
>
>> > > requires: bash cygwin libgcc1 coreutils
>>
>> And you should be omitting the 'requires: cygwin' dependency as
>> redundant,
>> now that upset/setup.exe guarantees it.
>
> Does that hurt anyt
At 08:01 AM 2/17/2010, Eric Blake wrote:
> > requires: bash cygwin libgcc1 coreutils
And you should be omitting the 'requires: cygwin' dependency as redundant,
now that upset/setup.exe guarantees it.
Does that hurt anything or is it just style?
Pierre
According to Christopher Faylor on 2/16/2010 3:29 PM:
> Actually:
>
> 6c6
> < requires: bash cygwin
> ---
> > requires: bash cygwin libgcc1 coreutils
And you should be omitting the 'requires: cygwin' dependency as redundant,
now that upset/setup.exe guarantees it.
--
Don't work too hard
