Re: EULA changes in svn

Package authors can't force an update to a newer micro version, ie,
there's no way to say "please ensure user has 1.2.4 or above". You can
only do that with new minor versions, eg, 1.4.

Generally, new APIs should go into new minor releases.

On 9/3/07, Curtis L. Knight <[email protected]> wrote:
> On 9/2/07, Mike Hearn <[email protected]> wrote:
> > 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.
>
> Hello Mike,
>
> I do not have great experience with respect to API changes but as
> these are new items they do not effect the current API. I was trying
> to see if there was some other nuance but maybe you can point one out.
>
> Some upcoming or current svn changes that are additions:
> package search command - in svn
> package update command - not yet in svn
> EULA support - for installation in svn, for execution not yet in svn
> XDG environment variables - not yet in svn
> configuration files change to /etc/xdg/autopackage - no yet in svn
>
> Regards,
> 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]