Sriram Natarajan wrote:
> Hi
>  Is there a how to / must read  / FAQ section for newbie package 
> maintainers ? 

Internally there is the gate README. It does need to be cleaned
up and pushed out (hardcoded paths and build machine names
aren't that useful, nor may my historical ramblings :) Maybe
the non-release specific bits should just be in the repository.

I was trying to look at the build instructions link

        http://opensolaris.org/os/project/sfwnv/install_quickstart/

but it appears to be broken. aha that's just the link in the text,
the one on the left side is ok:

http://www.opensolaris.org/os/project/sfwnv/Documents/install_quickstart/

I think I just fixed it anyway. or broke it horribly.


>  I was going through sfw-nv source tar ball and its related scripts for 
> various sub components that gets bundled as part of sfw consolidation. 
> Currently, the convention seems to be that the 'install' component 
> script shipped within 'sfw' consolidation manually sets the permission 
> for every file rather than simply doing something like 'chmod -R 644' of 
> an entire directory.  Is there any specific reason as to why this method 
> is preferred ?

Several reasons.

1. because each thing should really touch its own files not others. this
    is probably the best reason.
2. chmod -R 644 on a directory may be fine if only your own files are
    there, but if other things put files with different permissions there
    too then you've just broken them when the full build is run.
    And since we build in parallel this can be a sometimes-you-see-it
    -sometimes-you-don't bug, which is very annoying. I seem to remember
    there could be a race in chmod itself too, where it stat's things
    before doing the chmod - if other bits of the build are adding
    and removing things while your chmod -R is running chmod could error
    out.

probably more I'm not remembering too.

Note that I'm no longer sure making the permissions match is all that
important, but someone may remember why they should be :) Also note
that Norm added some new scripts to help with this. Look at
install-proto/protofix in usr/src/tools and their use in something
like cmd/a2ps.

        Mike

Reply via email to