launchpad-dev team mailing list archive

[Robert Collins <robert.collins@xxxxxxxxxxxxx>]

On Wed, Nov 3, 2010 at 2:58 AM, Marc Tardif <marc.tardif@xxxxxxxxxxxxx> wrote:
>> - we don't have a
>> good story for working with packages like that, and it would be much
>> easier if your package was lpSOMETHING instead - for now.
>
> There is no rush to publish my project on pypi.python.org, so I would
> like to help build a good story. For example, I have a recurring dream
> of extracting the Librarian from Launchpad as a standalone project. Would
> having two projects under the lp namespace help build this story?

Its a toolchain thing: need to make sure that the packages import
correctly even though there isn't a 'namespace package' for lp - and
as the main lp tree contains lp itself, thats nontrivial. Other
projects I've seen do this late in the piece have suffered significant
disruption in making it work.

If you wish to do the work, thats fine with me, but I wouldn't want to
see disruption to our developers or development process for this
low-return thing at this point. We've no interest in Launchpad itself,
or related Launchpad specific elements being published as packages :
Launchpad is intended as a live-deployment product deployed on
launchpad.net. We don't deploy the lp tree itself as a package, though
we do deploy its dependencies as (variously) eggs/debs.

The lazr namespace is where (most) spinoff projects of Launchpad are
published, though as you say, the tracker you've built is Launchpad
specific, and lazr is generic.

-Rob