Re: install/46482: wrong directory to pkgsrc tarball in sysinst

[Jeff Rizzo <riz%netbsd.org@localhost>]

The following reply was made to PR install/46482; it has been noted by GNATS.

From: Jeff Rizzo <riz%netbsd.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: "Jeremy C. Reed" <reed%reedmedia.net@localhost>, 
install-manager%netbsd.org@localhost
Subject: Re: install/46482: wrong directory to pkgsrc tarball in sysinst
Date: Sun, 27 May 2012 09:20:35 -0700

 On 5/26/12 5:20 PM, Jeremy C. Reed wrote:
 > The following reply was made to PR install/46482; it has been noted by GNATS.
 >
 > From: "Jeremy C. Reed"<reed%reedmedia.net@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc:
 > Subject: Re: install/46482: wrong directory to pkgsrc tarball in sysinst
 > Date: Sat, 26 May 2012 19:17:21 -0500 (CDT)
 >
 >   >   >  The menu does not allow choosing file name.
 >   >   this could be changed. But should it? We don't allow choosing the rest 
 > of the
 >   >   filenames, though you could argue that choosing an older pkgsrc 
 > release would
 >   >   be useful.
 >
 >   No it is not needed. I am not requesting it.
 >
 >   >   I'm rather interested in what caused this... For pkgsrc-2011Q4, 
 > apparently
 >   >   there were symlinks created, for the latter ones not.
 >   >   Which policy should go first, filenames or namings in sysinst?
 >
 >   I guess symlinks can be made and then some tool to check them daily to
 >   make sure exists.
 >
 >   I see now that the current/ directory does have the symlinks but the
 >   stable/ directory does not.
 >
 >   I can probably make the symlinks myself, but I don't know if something
 >   will end up replacing them.
 >
 
 This would be my fault;  I created the symlinks by hand when adding the 
 pkgsrc functionality, but did not ensure they existed in all 
 directories.  The correct fix would be to make sure they exist (and that 
 any automated processes re-create them when new directories are made).