Re: EULA changes in svn

Shouldn't new API features like that go into 1.4?

On 9/2/07, Curtis L. Knight <[email protected]> wrote:
> On 9/2/07, Isak Savo <[email protected]> wrote:
> > The recent problems with non-working mkapspec packages indicates a
> > problem with the new EULA support.
> >
> > Curtis, correct me if I'm wrong here, but it looks like packages build
> > against autopackage svn (to be 1.2.5) will not be installable on 1.2.4
> > and earlier systems. If this is true, then we have two options:
> >  1) Roll back the EULA changes and put them in an unstable devel
> > branch. This branch would then eventually end up as autopackage 1.4
> >  2) Fix the EULA code so that it doesn't break on 1.2.4 and earlier systems.
> >
> > I'd love to see 2) happen, cause that means people will instantly
> > benefit from the work Curtis has done with the EULA support. Is it
> > possible?
>
> Hey Isak,
>
> Thanks for catching that item for me. What you are describing is that
> the backend.template is looking for a function that does not exist
> before svn/1.2.5. I can add a version check for 1.2.5 and api target
> 1.2 to enable this function if the package metadata is proper. I think
> your 2) can happen without issues unless you see further items.
> Realistically, I might not have the EULA support at runtime but the
> support code makes that available so no other template changes will be
> needed.
>
> I will probably add this new check later today.
>
> Enjoy,
> Curtis
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected]
> For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected]
For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]