[sugar] packaging python

[Neal Norwitz]

On 3/6/07, Marco Pesenti Gritti <mpg at redhat.com> wrote:
>
> > Also, for something like PGO, I would make a separate target or two in
> > the makefile, but it wouldn't be the default target.  Is that a
> > problem?  I'm currently thinking about 2 options, make pgo-fast and
> > make pgo-complete.  The fast target would just run python a bit (ie,
> > use the existing run when building all the modules).  The complete
> > target would run the regression test suite which will take an
> > additional 5 minutes or so depending on your box.
>
> I'm not sure how we want to go about this exactly.
>
> Usually we are trying to reuse Fedora packages to avoid additional
> maintenance work. When the changes are generally useful I think we
> should just try to get them upstream.

Agreed.  The problem will be that any performance changes will
probably only be applied to the trunk and not back ported to 2.5.  I
suppose we can deal with that latter.  First, I'll work on the items
you suggest from the other thread we have dealing with performance.

> For OLPC specific customizations, personally I think we should verify
> they actually improve performance of sugar or of the activities before
> deciding to maintain our own package.

Definitely.

Cheers,
n