On Mon, Jun 26, 2017 at 01:46:05PM +0200, Landry Breuil wrote:
> On Mon, Jun 26, 2017 at 12:36:16PM +0200, Marc Espie wrote:
> > I need to get this thru my next bulk.
> > This should work around several existing issues.
> > 
> > First, PKGDIR must exist.  Creating it during fake is no longer possible,
> > because this doesn't work with dpb in privsep mode.
> > 
> > Having PKGDIR not be a directory/pointing in the wrong location means you
> > might miss MESSAGE/UNMESSAGE (which are not even written down in the PLIST)
> > or miss MESSAGE/RCscripts which must exist in the PLIST.
> > 
> > The more ambitious change involves changing the flow of creating new ports
> > to make it slightly faster.
> > 
> > Mainly, READMEs and RC installation is not really tweakable, since it 
> > happens
> > at the end of fake. So instead of doing it during fake, do it prior to
> > update-plist and package itself and (that's the cool part) do NOT generate
> > a cookie.   So it will happen each and every time. Accordingly, wipe 
> > existing
> > readmes and rc (this assumes RCDIR in the fake area is initially empty,
> > which should always be the case).
> > 
> > That way, a porter should be able to tweak the readmes/rc, add variables, 
> > add variable values, and quickly regen packages without having to wipe 
> > fake and redo it each time, which is a win.
> 
> Oooh yea that's a win ! I suppose rc scripts and README paths will survive 
> make
> update-plist once the latter is redone from scratch ?

I'm not sure I understand your question.

Right now, I'm not touching update-plist, it's meant for later, once I dig
up the new and improve prototype, which just isn't usable right now, but
does lots of things right, so will be much less of a mess once it's
finished.

Reply via email to