Re: cvs commit: src/nrelease Makefile

[Chris Pressey <cpressey@xxxxxxxxxxxxxxx>]

On Sun, 10 Apr 2005 17:04:17 -0400
David Rhodus <sdrhodus@xxxxxxxxx> wrote:

> On Apr 10, 2005 4:58 PM, Chris Pressey <cpressey@xxxxxxxxxxxxxxx>
> wrote:
> > On Sun, 10 Apr 2005 16:50:53 -0400
> > David Rhodus <sdrhodus@xxxxxxxxx> wrote:
> > 
> > > On Apr 10, 2005 4:44 PM, Chris Pressey <cpressey@xxxxxxxxxxxxxxx>
> > > wrote:
> > > > On Sun, 10 Apr 2005 16:37:23 -0400
> > > > David Rhodus <sdrhodus@xxxxxxxxx> wrote:
> > > >
> > > > > On Apr 10, 2005 4:33 PM, Chris Pressey
> > > > > <cpressey@xxxxxxxxxxxxxxx> wrote:
> > > > > > On Sun, 10 Apr 2005 13:27:32 -0700 (PDT)
> > > > > > David Rhodus <drhodus@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> > > > > >
> > > > > > > drhodus     2005/04/10 13:27:32 PDT
> > > > > > >
> > > > > > > DragonFly src repository
> > > > > > >
> > > > > > >   Modified files:
> > > > > > >     nrelease             Makefile
> > > > > > >   Log:
> > > > > > >   Add in a 'livecd' taget for those who don't want to
> > > > > > >   include the installer program in their ISO image file.
> > > > > > >
> > > > > > >   Revision  Changes    Path
> > > > > > >   1.31      +7 -1      src/nrelease/Makefile
> > > > > > >
> > > > > > >
> > > > > > > http://www.dragonflybsd.org/cvsweb/src/nrelease/Makefile.diff?r1=1.30&r2=1.31&f=u
> > > > > >
> > > > > > This shouldn't be necessary... the existing 'make release'
> > > > > > has always been able to make a LiveCD ISO without the
> > > > > > installer.
> > > > > >
> > > > > > -Chris
> > > > > >
> > > > >
> > > > > How so ?  I don't see a way to build a ISO image without the
> > > > > installer unless one edits the Makefile.
> > > >
> > > > release:        check clean buildworld1 buildkernel1 \
> > > >                 buildiso customizeiso pkgaddiso mklocatedb mkiso
> > > >
> > > > There's nothing installer-related in there.
> > > >
> > > > -Chris
> > >
> > > Yes there is, 'check' requires several packages before proceeding
> > > on to making the ISO image file.
> > 
> > Only cvsup-without-gui and cdrtools, which are not installer
> > related.
> > 
> > -Chris
> 
> 
> .for PKG in ${REL_PACKAGES}
>         @if [ ! -f ${PACKAGES_LOC}/${PKG}.tgz ]; then \
>                 echo "Unable to find ${PACKAGES_LOC}/${PKG}.tgz.  This
>                 is"; \ echo "typically accomplished by cd'ing into the
>                 appropriate"; \ echo "port and typing 'make
>                 installer_fetchpkgs'"; \
> 
> fetchpkgs is going to put the installer on the CD because its in this
> list. INSTALLER_PKGS= libaura-3.1 libdfui-4.1 libinstaller-5.1 \
>                 dfuibe_installer-1.1.6 dfuife_curses-1.5 \
>                 thttpd-notimeout-2.24 dfuife_cgi-1.4

REL_PACKAGES != INSTALLER_PKGS unless you use one of the installer_*
targets.  If you just use 'make release', REL_PACKAGES = REQ_PACKAGES.

> Point is I don't want to have to deal with ANY packages when building
> a ISO especially when I am using the CD to test booting DFly on a new
> hardware platform for the first time.