Re: AP v1.4.1: Dependency Building: Broken
Jan Niklas Hasse <[email protected]> Sun, 24 May 2009 22:27:56 +0200
| Newsgroups | gmane.comp.autopackage.devel |
|---|---|
| Message-ID | <[email protected]> |
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.=C2= =A0 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. >> Okay, I've fixed it in r2564. I can't make an release because I'm >> visiting my brother for two days and will be back Friday night. I will >> try my best to release 1.4.2 then. > > No worries; as I can still use v1.4.1 for distributed packages with v1.2.= 6 > for remote dependencies, the release of v1.4.2 isn't urgent. That's good to hear. Anyway I've released 1.4.2 just now (still some problems with the developer tools, give me a second). --------------------------------------------------------------------- To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected] For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]