Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 7 Jan 1998 13:26:53 -0800
From:      John-Mark Gurney <gurney_j@efn.org>
To:        Mikhail Teterin <mi@aldan.algebra.com>
Cc:        freebsd-bugs@freebsd.org
Subject:   Re: misc/5369
Message-ID:  <19980107132653.01148@hydrogen.nike.efn.org>
In-Reply-To: <199801072043.PAA00369@rtfm.ziplink.net>; from Mikhail Teterin on Wed, Jan 07, 1998 at 03:43:06PM -0500
References:  <19980107115721.40442@hydrogen.nike.efn.org> <199801072043.PAA00369@rtfm.ziplink.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Mikhail Teterin scribbled this message on Jan 7:
> John-Mark Gurney once stated:
>  
> => Yes, I know :) But just plain ``make installworld'' -- will it install
> => properly after this sort of ``buildworld''?
> =
> =yes.... installworld simply "installs" it all...  and will use default
> =permissions...  nothing is copied over...  (look at the Makefile :) )
> 
> So, if I change the permissions/ownerships in the tmp-tree (by changing
> make's variables or after the buildworld) installworld will not install
> properly?
> 
> => =why specificly is it a workaround?  also, how to do you expect to modify
> => =the buildworld target so that it redefines all the user/group options?
> => 
> => Do not alter the permissions/ownerships in the buildworld stage at
> => all. Then, the install will not try to do anything illegal, will
> => it?
> =
> =installworld actually uses the sources that were built, the installed
> =tree under .../tmp (which was the problem in buildworld) isn't used
> =except to run make...  and the permisions you modified in the
> =installworld are relegated to the .../tmp tree...
> 
> Seems, like the job of setting permissions and ownerships should be migrated
> from buildworld to installworld. Right?

guess you misunderstood me....  look at this section of the makefile:
        @echo "--------------------------------------------------------------"
        @echo " Making hierarchy"
        @echo "--------------------------------------------------------------"
        cd ${.CURDIR} && ${MAKE} hierarchy
        @echo
        @echo "--------------------------------------------------------------"
        @echo " Installing everything.."
        @echo "--------------------------------------------------------------"
        cd ${.CURDIR} && ${MAKE} install
        @echo
        @echo "--------------------------------------------------------------"
        @echo " Rebuilding man page indexes"
        @echo "--------------------------------------------------------------"
        cd ${.CURDIR}/share/man && ${MAKE} makedb

notices the install target...  the ONLY time the installworld target
uses the files that were installed in buildworld, is the make program...
everything else is pulled from the obj directories...  (which were never
"installed" in the buildworld target)...

so, installworld will be successful and run properly as long as you don't
pass any *BIN, *GRP options, it is NOT apart of the world target..

please at least look at the makefiles...  it's not much different than
a shell script...

-- 
  John-Mark Gurney                          Modem/FAX: +1 541 683 6954
  Cu Networking					  P.O. Box 5693, 97405

  Live in Peace, destroy Micro$oft, support free software, run FreeBSD



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980107132653.01148>