You might find the work that I am doing to upgrade some of the SFW 
printing bits useful.  I am looking to introduce two useful tools.

The first (install-proto) is a resplacment  for install/install-sh/... 
that you can use with configure/make install/... to install the bits in 
the proto area instead.  So even if your open source package doesn't 
honor DESTDIR, this install will deal with it.  It will also perform the 
various post processing that we do on scripts/binaries/...

The second tool (protofix) is a little toy that fixes the proto area 
permissions (and potentially owner/group) to match the package 
prototypes.  This has greatly simplified my upgrade work.

An example of an install target for a2ps looks like this

    install: all
            # install the bits in the proto area
            cd $(VER); env SRC=$(SRC) DESTDIR=$(ROOT) \
                    MANSCRIPT=../../sunman-stability \
                    make install
            # fix the proto area
            $(SRC)/tools/protofix --pkg SUNWa2psr --pkg SUNWa2psu --perm
            # clean up the turds
            $(RM) -f $(ROOT)/usr/lib/liba2ps.a $(ROOT)/usr/lib/liba2ps.la \
                     $(ROOT)/a2ps.el $(ROOT)/a2ps-print.el

instead of a lengthly install-sfw script.

The webrev is at (sorry, only internally available for now)
    http://abelia.sfbay/builds/jacobs/nv/sfwnv-print/webrev/

    -Norm

PS.
    I also have a tool that generates package info/proto files based on 
a proto area.  It is similiar to pkgproto, but it gets the 
owner/group/perm for shared bits from the system, assumes root/bin for 
the rest and removes write bits from virtually everything.  I use is as 
a starting point to update my package prototypes.



Bart Smaalders wrote:
>
> I'm working on getting wireshark integrated into sfw.... and I'm
> wondering:
>
> Given that we normally run builds as non-root, is it still important
> that root builds install w/ the correct owners and modes?
>
> I'm wondering because I can use DESTDIR to install using the
> install target in the package, but the modes/owners don't
> match Solaris defaults when run as root.
>
> Given that wireshark installs some 170+ files, I'd much
> prefer not to cons up my own install target.
>
> Thoughts?
>
> - Bart
>
>
>


Reply via email to