Re: Problems: Stability: 1.4.0

>
> You're right, it was pretty easy to fix. Thank you so much for finding
> this. I don't know why I haven't noticed it. It was caused by using the
> wrong variable and I fixed it in revision 2543:
> http://trac.autopackage.org/changeset/2543
>

Thanks for testing this bug and for making the necessary modification.

I think Eugene is right, this is related to #43.
>

I've added our quotes to the #43 ticket in a new comment.


> Ah, I just found out. I missed to add it to the makefile which installs the
> development files. Also fixed in r2543.
>

Thanks for testing this bug and for making the necessary modification.

Great! But before you upgrade the code from Qt3 to Qt4 wait till I posted
> some news about my plans for Autopackage >=1.5. It contains some major
> changes which should make it possible for you to program in python-qt4.


I'd like to port the AP-Qt front-end to PyQt4, but it'd require that the
end-users have Python and PyQt4 pre-installed.  In many cases, this test
would fail and the AP-Gtk front-end would be used instead.

 For now we should concentrate on getting the Qt3 front-end to work. Do you
> think it would be okay if we release 1.4.0 without the Qt3 front-end and add
> it later on?


Yes, I think that's a good idea: wipe out AP-Qt until it's identical to
AP-Gtk again.  Since I've started teaching and tutoring again, I probably
won't have much time to modify AP-Qt right now.


> I will build Autopackage again in the next days and fix a last bug I've
> found (package can't be found after installing the support code).
> Unfortunately I'm in my last year of school and most of the time busy
> studying.


As a teacher, I must advise you to give priority to your studies :-).  We're
lucky to have you as an AP developer, and there's no urgency to release v1.4
since v1.2.6 seems to be quite stable.