[OpenAFS-port-darwin] Re: anyone want to work on the installer?

[David Botsch]

In the custom installer we made, the gui config utility (included as a 
binary, which, I believe, was the intention here) is only run from the 
postinstall, not the postupgrade (so that upgrades keep the same 
settings as before).

In our case, the install instructions say something like, "when you see 
the screen prompting you for a cell name, type in "msc.cornell.edu" and 
then click NEXT"


On 2004.08.05 15:23 Everette Gray Allen wrote:
> Ok so my bad phrasing of the question has confused several folks.  
> Sorry for that.  Let me clarify my question.
> Right now there is no postflight script in the stable release 
> installer.  The proposal is to add a postflight script.  My concern 
> is: 1) I am not sure what it would do ? and 2) I like the idea that I 
> can simply add my own postflight without having to be concerned that 
> something critical to the stock openafs install would be left out or 
> misconfigured.
> 
> I did not understand the comment about this "cell discovery" tool 
> which needs command line xcode to build.  It looked like from the 
> comment that the tool might need to be built on the fly from the 
> postflight script in the installer.  I believe that the proposal is 
> to include the "cell discovery" tool in the installer as a binary and 
> call it from the postflight to create a valid ThisCell file.  I 
> already handle that problem by copying over the valid ThisCell for 
> our site when I customize the "stock" installer.
> 
> So I guess I do not understand why we need the postflight script? and 
> I selfishly don't want the addition of a postflight to mess up the 
> ease at which I customize the present installer.
> If the postflight just does configuration tasks then maybe I could 
> just remove it and drop my script in with no harm.  On the other 
> hand, postflight runs every time, regardless of upgrade or new/clean 
> install and that could be a problem for folks in general who are 
> upgrading and have made changes to ThisCell or CellServDB or whatever 
> configs are attempted by the proposed postflight.
> 
> 
>> On Tue, 3 Aug 2004, Everette Gray Allen wrote:
>> 
>>>> So I assume that this question is in context of making this app 
>>>> and not building the installer.  I believe it would not be safe to 
>>>> assume that
>> 
>> 
>> building the installer, not installing it. if you don't have 
>> developer tools installed, i don't care if you can build an 
>> installer.
>> 
>> 
>>>> everyone has the Developer tools installed.  Personally I have 
>>>> been adding my own postflight script to the "stock" install to add 
>>>> all the needed files (ThisCell, TheseCells, CellServDB, 
>>>> afsd.options) for my site including a edu.mit.kerberos file and an 
>>>> aklogin.logout plug-in so I am hoping that a new postflight script 
>>>> would not add important install items but only easily replaceable 
>>>> configuration items? In other words I want to be able to rip out 
>>>> the "stock" postflight and add mine back without worry the install 
>>>> will not be complete.
>> 
>> 
>> if you can modify an installer now, i have no mechanism to make it 
>> so you can't later. (and clearly you can, and clearly i can't:-)
>> 
>> you're just untarring, adding something, mucking with postflight, 
>> and closing it. if we call this from postflight, well, you're of 
>> course free to remove it. but that's orthogonal to building an 
>> installer, since obviously you just told us you aren't.
> 
> 
>-- 
> Everette Gray Allen		Systems Programmer II
> ITD Computing Services	Macintosh Support Specialist
> 2620 Hillsborough St, Campus Box 7109
> Raleigh, NC 27695-7109
> 919-515-4558		Everette_Allen@ncsu.edu
> 
> _______________________________________________
> port-darwin mailing list
> port-darwin@openafs.org
> https://lists.openafs.org/mailman/listinfo/port-darwin

-- 
********************************
David William Botsch
Consultant/Advisor II
CCMR Computing Facility
dwb7@ccmr.cornell.edu
********************************