tech-toolchain archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: updating a piece of the running system from is too hard

David Holland <> writes:

> On Fri, Feb 26, 2010 at 01:36:44PM -0500, Greg Troxel wrote:
>  > > I think that it would be useful to have a simple way of telling
>  > > ${TOOLDIR}/bin/nbmake-${MACHINE} to install as if MKUNPRIVED had not
>  > > been set at the time the wrapper was created.  I haven't thought enough
>  > > about how to do that.
>  > 
>  > "sudo nbmake-$arch DESTDIR=/ MKUNPRIVED=no install" seems to do exactly
>  > this but I'm not 100% certain.  I propose
>  > 
>  >   sudo nbmake-$arch live-install
>  > 
>  > to be an equivalent shortcut.
> ISTM (if we're talking about rearranging stuff) that this should be
> "install", and the install that goes into $OBJ/destdir.$ARCH/...
> should be called something else, like stage-install or install-staging
> or whatnot.

I disagree, because there is historically one notion of install and the
destdir setup as part of and make variables says where that
goes.  install should go into DESTDIR, always.

What I was trying to do is say

  I know the build was set up to go to DESTDIR, and UNPRIVED, and I know
  that I could set USETOOLS=no and redo the build and install normally,
  but what I want now is to reuse the existing build and do an
  installation into a different place, without UNPRIVED.

> A full build should always build into the local destdir (and IMO it
> should always use METALOG, but that's a separate discussion) and not
> touch the ultimate destdir (which is usually /) until its final
> install phase. However, if I manually do 'make && make install'
> somewhere it normally means I want to install directly into the
> ultimate destdir.

Sometimes for me it means I want to just freshen the configured destdir.

Attachment: pgpLN0UjY5Tzf.pgp
Description: PGP signature

Home | Main Index | Thread Index | Old Index