Base Package Origins

[Glen Barber]

On Tue, Apr 26, 2016 at 05:08:39PM -0300, Renato Botelho wrote:
> > On Apr 26, 2016, at 16:53, Glen Barber <gjb at FreeBSD.org> wrote:
> > 
> > On Tue, Apr 26, 2016 at 03:47:14PM -0400, Kris Moore wrote:
> >> On 04/26/16 03:40 PM, Renato Botelho wrote:
> >>>> On Apr 26, 2016, at 14:54, Kris Moore <kris at ixsystems.com> wrote:
> >>>> 
> >>>> 
> >>>> So, we're in the process of moving to package base for PC-BSD -CURRENT
> >>>> images next month. The only real nit I'm seeing so far is that each
> >>>> package has a origin of 'base'. Shouldn't that be unique for each
> >>>> package? I.E. base/FreeBSD-<foo>
> >>> Hi Kris,
> >>> 
> >>> We are working to move pfSense 2.4 development snapshots to 11 with base package as well
> >>> 
> >>> How are you dealing with files installed by distrib* targets? (/etc/rc, /etc/master.passwd, …)
> >>> 
> >> 
> >> I've looked at a kludge to ship those bits as another .txz. Did you have
> >> another method, or is this something we can expect fixed properly as a
> >> package, I.E. FreeBSD-distrib-FOO.txz
> >> 
> > 
> > One (other kludge) I was considering was automatically invoking
> > etcupdate(8) on 'FreeBSD-runtime' installation, which should
> > automatically populate /etc on a clean install, as well as keeping /etc
> > updated as part of upgrades.
> > 
> > But, I *really* do not like that idea...
> 
> That was the only idea I had too. Why don’t you like it?
> 

If there is a merge conflict, it enforces interactive resolution.

Glen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-pkgbase/attachments/20160426/83444e5b/attachment.sig>