On 2017-05-24 20:07, Doug Henderson wrote:
> , On 24 May 2017 at 18:16, Brian Inglis wrote:
>> I would appreciate it if anyone has any experience with, or can point me
>> to, any python3 code in any Cygwin package which works Windows proxy
>> authentication?
> I had a glance at the source. I
, On 24 May 2017 at 18:16, Brian Inglis wrote:
> I would appreciate it if anyone has any experience with, or can point me
> to, any python3 code in any Cygwin package which works Windows proxy
> authentication?
I had a glance at the source. I recall adapting it to load SQL tables
with units
On 2017-05-24 12:13, Achim Gratz wrote:
> Brian Inglis writes:
>> Updating the currencies only when setup is run seems to me to be
>> insufficient if users want to use current currency conversions.
>
> Well yes. But that means that each user should be able to update, not
> just the
Brian Inglis writes:
> Updating the currencies only when setup is run seems to me to be
> insufficient if users want to use current currency conversions.
Well yes. But that means that each user should be able to update, not
just the administrator.
> Would the best approach be to punt on running
Buchbinder, Barry (NIH/NIAID) [E] writes:
> I would prefer that by default updates happen automatically and those
> who do not want automatic updates do something to stop them from
> happening.
That there should be updates was never debated, only the machanism of
doing so is discussed here.
>
On 2017-05-24 10:26, Buchbinder, Barry (NIH/NIAID) [E] wrote:
> Brian Inglis sent the following at Tuesday, May 23, 2017 10:37 PM
>> On 2017-05-23 17:55, Doug Henderson wrote:
>>> On 23 May 2017 at 15:49, Brian Inglis wrote:
Updating the currencies only when setup is run seems to me to be
Brian Inglis sent the following at Tuesday, May 23, 2017 10:37 PM
>
>On 2017-05-23 17:55, Doug Henderson wrote:
>
>> On 23 May 2017 at 15:49, Brian Inglis wrote:
>>
>>> Updating the currencies only when setup is run seems to me to be
>>> insufficient if users want to use current currency
On 2017-05-23 17:55, Doug Henderson wrote:
> On 23 May 2017 at 15:49, Brian Inglis wrote:
>
>> Updating the currencies only when setup is run seems to me to be
>> insufficient if users want to use current currency conversions.
>
> Currencies needs to be split to a different package from
On 23 May 2017 at 15:49, Brian Inglis wrote:
> Updating the currencies only when setup is run seems to me to be
> insufficient if users want to use current currency conversions.
Currencies needs to be split to a different package from non-currency
units. Non-currency units is very static,
On 2017-05-23 11:28, Achim Gratz wrote:
> Brian Inglis writes:
>> The easiest approaches to this would be:
>> - rename or delete postinstall script which might upset cygcheck or
>> setup remove
>> - null /usr/share/units/currency.units, as it is required and produces
>> an error message if not
Brian Inglis writes:
> The easiest approaches to this would be:
> - rename or delete postinstall script which might upset cygcheck or
> setup remove
> - null /usr/share/units/currency.units, as it is required and produces
> an error message if not available, but if it is empty, everything works.
On the cygwin list, Achim Gratz asked:
> Can you please make that configurable by some file in /var/lib/units
> that will prevent the perpetual postinstall script from even forking
> if the user decides that this should not be updated?
Configuration of units is currently supported only in
12 matches
Mail list logo
