On Thu, Jan 7, 2010 at 11:34 AM, Marius Vollmer
<marius.voll...@nokia.com> wrote:
> Currently, is_python_package looks like this:
>
> sub is_python_package {
> my ($dir) = @_;
>
> # XXX - some input from Pythonistas is required here.
>
> return (-d "$dir/usr/lib/python2.5"
> || -d "$dir/usr/share/pyshared"
> || -d "$dir/usr/share/pyshared-data"
> || -d "$dir/usr/lib/pyshared"
> || -d "$dir/usr/share/python-support"
> || -d "$dir/usr/lib/python-support");
> }
>
> I will change that to something closer to what has actually been
> proposed. Concrete patches are most welcome, of course!
That's almost the same directories currently handled by pymaemo-optify:
https://garage.maemo.org/svn/pymaemo/packages/pymaemo-optify/trunk/debian/default/pymaemo-optify
As a test, you could run it on all python-* .deb packages currently in
the repository, and see if it catches all/most of them. If it works,
and is used only to skip Python packages from automatic optification,
I *personally* see no problem.
It would be nice to have a option to force optification, even if the
heuristics says to ignore the package. I've seen some Python packages
that had no problems with automatic optification, so that way they can
still use maemo-optify.
BTW, if/when autobuilder changes to automatically optify packages with
no debian/optify entry, will it be done only for the newer uploaded
packages?
IMHO running optify on the live packages might break things. If it is
run only on newer packages, developers have the chance to report
auto-optify related problems.
Regards,
--
Anderson Lizardo
OpenBossa Labs - INdT
Manaus - Brazil
_______________________________________________
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
