launchpad-dev team mailing list archive

[Maris Fogels <maris.fogels@xxxxxxxxxxxxx>]

Hi Paul, thank you for looking into this.  I'll gladly help in any way I can.


On 09/15/2010 02:14 PM, Paul Hummer wrote:
> Hi Gary and Maris (and other Launchpad devs):
> 
>   The lazr-js build system is starting to get a little long in the
> tooth.  One of the biggest issues we've had recently is managing the
> python dependencies that go along with the sdist, specifically in how
> the dependencies differ between launchpad and landscape.
> 

Could you please go into a bit more detail about the problems you faced with
dependencies?

FWIW, lazr-js produces an sdist because Launchpad uses both the lazr-js Python
and lazr-js JavaScript sources.  A sdist was the easiest way to reuse both
parts.  We can change that decision, but it will take some work (more on that
below).

If we want to switch the lazr-js project over to to using .tar.gz and/or debs
for release, that would be fine by me - in fact, I think it could help adoption
by simplifying integration of the lazr-js JavaScript.  As an added bonus, U1
already has code we could borrow for creating lazr-js debs for their system.

The problem is what do we do about Launchpad's direct use of the lazr-js Python
tools?  Right now Launchpad uses the lazr-js Python toolchain for the bin/jslint
and bin/jsbuild commands.  We need some way to keep these functions available in
Launchpad for use with our own JavaScript sources.

  One option is to create our own copies of these commands and stop relying on
lazr-js altogether.  Another other option is to turn the commands into a new
Python library outside lazr-js, then have both the lazr-js project and the
Launchpad project depend upon it.  I don't know which approach is better: both
have pros and cons.


>   I wonder if it would be better if we could just store the lazr-js
> directly in our tree.  I think it would go a long way to making it
> easier to upgrade lazr-js in Launchpad (and reduce complication in both
> the lazr-js and launchpad build systems).

I am not sure what you mean by "store lazr-js directly in our tree".  If you
mean "only use the lazr-js JavaScript sources in our tree", then yes, we can do
that, with the previously mentioned caveat about keeping the jslint and jsbuild
commands working.


-- 
Māris Fogels -- https://launchpad.net/~mars
Launchpad.net -- cross-project collaboration and hosting

Attachment: signature.asc
Description: OpenPGP digital signature