This is the mail archive of the
mailing list for the Cygwin project.
Re: units issues
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin-apps at cygwin dot com
- Date: Tue, 23 May 2017 19:28:34 +0200
- Subject: Re: units issues
- Authentication-results: sourceware.org; auth=none
- References: <c2742327-a4d3-6e3c-88ad-5cf95af89b8a@SystematicSw.ab.ca> <firstname.lastname@example.org> <e65a0c0b-737e-2d10-b5c9-ef1ee5d6f99d@SystematicSw.ab.ca> <7f2814c4-518a-c097-de05-f4c694dbf362@SystematicSw.ab.ca> <email@example.com> <b2d200f9-2401-50a2-ecc3-567fcad95923@SystematicSw.ab.ca> <f16d69d5-9b9b-0089-b73a-2b0abdc0ce3d@SystematicSw.ab.ca> <firstname.lastname@example.org> <977d9380-31dc-78de-a260-16689664129d@SystematicSw.ab.ca> <5d9a21b5-2c14-c1e8-2c33-6038aef22ace@SystematicSw.ab.ca>
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.
Nope. The user should not have to muck with packaged files at all.
> It is not very useful if not up to date (I run the update daily), and if
> not up to date, might as well be empty, but some opinions may differ.
The issue is that you cannot assume that postinstall scripts are able to
access the network at all. Where this isn't possible the administrator
will have to find a different way of keeping those files up-to-date
(which should also not be packaged), but that's something to maybe just
document. But you will have to provide some way of letting the user
specify if that updating is OK. If you want this to be possible during
the initial install you might even need to provide another sub-package
whose only purpose is to confer this decision (it could be empty and
just doing a simple postinstall action).
> In the postinstall script find which ensures updates happen at most daily:
I've asked specifically to structure any perpetual postinstall script in
a way that it doesn't do any non-necessary work, be it forking or
otherwise unless it is going to actually do something useful. A simple
file test that exits the postinstall script when the file is or isn't
there satisfies that constraint, running commands and scripts doesn't.
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld: