Re: [pkg-discuss] creation of 'flag files'

Fri, 10 Oct 2008 11:52:23 -0700

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.

thx,  --emk

Dan Price wrote: 
On Fri 10 Oct 2008 at 09:13AM, Ed McKnight wrote:
  
Danek Duvall wrote:
    
On Fri, Oct 10, 2008 at 08:38:04AM -0700, Ed McKnight wrote:

  
      
Gotta SVR4 package currently creating a flag file by /usr/bin/touch in 
postinstall. It could alternatively have been created 'directly' from an 
entry in the prototype file.
    
        
What's a "flag file"?
  
      
A file whose meaning is not in its contents but in its presence; 
typically an empty file.

thx,  --emk
    

Will you be deleting said file after performing some first-time
initialization?  Do you want it to come back after upgrades to the
package?

You might want to sketch out the scenario more completely.

        -dp

  
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to