Re: [1.26 1/1] setup.py update for 1.26 release

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Mon, 2015-04-20 at 13:32 +0100, Alex DAMIAN wrote:
> From: Alexandru DAMIAN <alexandru.damian@intel.com>
> 
> This patch updates setup.py and MANIFEST.in so it correctly
> packages bitbake in standard python package format.
> 
> Use "python manage.py sdist" to generate installation package.
> 
> Minor updates to toaster scripts so they work correctly
> from a package installation.
> 
> Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com>
> ---
>  MANIFEST.in                         | 207 ++++++++++++++++++++++++++++++++++--
>  bin/toaster                         |  31 ++++--
>  lib/toaster/toastermain/settings.py |   4 -
>  lib/toaster/toastermain/urls.py     |   3 -
>  setup.py                            |  16 +--
>  5 files changed, 232 insertions(+), 29 deletions(-)

We've been nervous about encouraging distros to ship packaged versions
of bitbake for some time. Things usually work better with the version
for the metadata you're using, not some random distro provided version.
We have been bitten by this a lot in the past. That said, we do have the
setup.py file and people do use it :/.

My other concern is the dependencies and the structure of this
packaging. I don't think bundling bitbake and toaster together is the
best move, I'd be much happier to see them packaged separately since
bitbake can happily be used without django, gobject and its other
dependencies.

I also noticed that ply and progressbar were dropped as requirements.
Whilst we ship copies of these with bitbake for simplicity, it was
previously a conscious decision not to package them and rely on the
upstream packaged version of them for the packaged version of bitbake.

Cheers,

Richard