Heads up: Poudriere changed default options dir

[Serpent7776]

On Tue, 14 Nov 2017 18:41:53 +0100
"Vlad K." <vlad-fbsd at acheronmedia.com> wrote:

> List,
> 
> before 3.2.0 Poudriere defined PORT_DBDIR with only 
> <jailname>-<setname>-options, which was apparently a bug. Now (in 3.2.0) 
> it honors -p option in the options command and includes ports tree name 
> (given to -p) in PORT_DBDIR.
> 
> In other words, if -p is given, it will be included in PORT_DBDIR. If 
> it's not, then nothing's changed.
> 
> The result of that is that it will mkdir 
> <jailname>-<treename>-<setname>-options, which has higher priority than 
> <jailname>-<setname>-options, so if you have the options dir created 
> from before, named only <jailname>-options (or 
> <jailname>-<setname>-options), it will now be overriden by the new 
> (correct) scheme.
> 
> This is important in my case, because when I first ran poudriere options 
> many lunar orbits ago, it created <jailname>-options, and 
> <jailname>-<setname>-options, and it remained like that as I don't have 
> more than one tree (but do have several jails and sets). So now it 
> "broke" my set up (which I suppose should be said it fixed a bug and my 
> setup was broken from before).
> 
> The fix was simply to rename the old <jailname>-options dir I had to 
> <jailname>-default-options (as "default" is my ports tree name), and 
> likewise for each set I use.
> 
> Sorry if this was mentioned before, though I found no public 
> announcement of this change. Thought it was important enough to mention 
> it, so here.
> 

Thanks for mentioning this. I wondered why poudriere is asking me to configure
each port after updating.
I think it should me mentioned in UPDATING.

-- 
/*
 * Serpent7776
 */