holland-discuss team mailing list archive

[Andrew Garner <muzazzi@xxxxxxxxx>]

I am not sure what the diff shows here.   holland.lib.common should
only have a few files under the holland/lib/ namespace.   This is a
"namespace package" and the __init__.py will effectively be empty -
these get handled by setuptools using some .pth magic.

The only overlap should be holland/lib/ which the "holland core"
defines a skeleton namespace for.

How you handle these at a distribution level is entirely up to you.
The RPM and debian packages create a "holland-common" package which
includes all the files that holland.lib.common and holland.lib.mysql
installs.  That would effectively be:

# holland.lib.common
holland/lib/compression.py
holland/lib/multidict.py
holland/lib/safefilename.py
holland/lib/which.py
holland/lib/archive/
# holland.lib.mysql
holland/lib/mysql/

You can split these out or combine them into other packages, if it
makes more sense to you.

If you are interested in what each package is installing you could use
the '--record' option with setup.py install:

$ python setup.py install --root=... ... --record=installed_files.txt

~Andrew

On Sat, Apr 7, 2012 at 7:37 PM, Alex Brandt <alunduil@xxxxxxxxxxxx> wrote:
> Hey Guys,
>
>
>
> I'm trying to update the holland ebuilds and have started noticing some
> interesting items when installing holland base and holland-lib-common. It
> appears they both want to install several files (see attached diff of the
> install directories) that are the same. Should these files be installed by
> the holland.lib.common or by holland itself?
>
>
>
> Thanks,
>
> --
>
> Alex Brandt
>
> Sales Engineer for Rackspace, RHCE
>
> http://www.alunduil.com
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~holland-discuss
> Post to     : holland-discuss@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~holland-discuss
> More help   : https://help.launchpad.net/ListHelp
>