Ed McKnight wrote: > I've been reminded that one valid user action is to delete this file, > hence it may be better for the file to be created in 'postinstall' > rather than delivered such that deletion might create a corrupt package > kind of state. The presence or absence of the file is essentially an > environmental control where a subsystem takes a cue from presence or > absence. > > Upgrade: interesting point. If the user has deleted the file it > shouldn't be recreated by next pkg operation. > > Note that the subsystems that read this flag file are not mine to > revise. An alternate design would read a value from the file, but that's > not what we have.
If your users are free to delete files at will, then things aren't likely to work no matter what the design. If your software needs to determine whether or not various components are installed, the "deliver an empty file" trick works fine... What does it mean if the user deletes the file but not the software? - Bart Bart Smaalders Solaris Kernel Performance [EMAIL PROTECTED] http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird." _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
