On Thu, Sep 15, 2005, David M. Fetter wrote:

> On Thu, 2005-09-15 at 07:21 +0200, Ralf S. Engelschall wrote:
> > On Wed, Sep 14, 2005, David M. Fetter wrote:
> >
> > > It doesn't seem that any fixes for the default path problem has been put
> > > into UPD, at least for OpenPKG 2.3.  Not sure if it was put into OpenPKG
> > > 2.4 because we haven't upgraded to that and we probably won't be able
> > > too until next year.  Are there any plans to add this as a UPD fix?  If
> > > not, then we will need to do something else on our side.
> >
> > I've not MFC'ed it as it is actually changing semantics and this way is
> > not backward compatible. Hence it could break an existing installation,
> > which should not happen for UPD packages.
>
> I thought the conclusive fix was an option that would disable those
> features, but by default they are on, therefore it won't break existing
> installations?

Oh, I see. Yes, you're right. My fault. I've forgotten that it was a
build-time option and disabled by default. Well, then we could MFC it,
yes.
                                       Ralf S. Engelschall
                                       [EMAIL PROTECTED]
                                       www.engelschall.com

______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
Developer Communication List                   openpkg-dev@openpkg.org

Reply via email to