Re: AP v1.4.1: Dependency Building: Broken

Jan Niklas Hasse wrote:
> On Fri, May 22, 2009 at 10:08 AM, Chris Giles <[email protected]> wrote:
>   
>>> You're right, it's my fault. I should have searched all files for
>>> "apkg-installer". Anyway, I will do my best to fix this today,
>>> although the damage is already done :(. I think the best solution is
>>> to add a legacy apkg-installer file into every package.
>>>       
>> I'll just rebuild all of my packages with AP v1.4.2 upon its release.  This
>> might prevent the need to keep the legacy "apkg-installer" file.
>>     
>
> Unfortunately not. Imagine someone has 1.4.1 installed and installs
> your package. 1.4.1 would still look for the apkg-installer file. So
> the first release I can "really" fix it is 1.6.
>   
If this is a real problem, you can force the package to require 1.4.2, 
even if 1.4.1 is installed. In apspec instead of %AutopackageTarget% put 
1.4.2 -- don't forget to update it when changing autopackage version.

That will trigger update of support code. (Normally only minor version 
change triggers it, 1.2 to 1.4 for example)

I wonder if breaking bugs like this should increment minor version, or 
if we need another number.

Something like that:

major.minor.patch.build
<very big changes>.<big changes>.<breaking bug fixes>.<nice to have bug 
fixes>

And make it so only change of the last number can be ignored.

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