[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [kobold@debian.org: The future of Zope{2, 3} and Plone in Debian and Ubuntu]




Hi,

On Sun, 04.10.2009 at 00:00:16 +0200, Jonas Meurer <jonas@freesources.org> wrote:
> thus we need to migrate our debian/rules to build zope2.12 with the help
> of buildout, whether we like it or not. unfortunately buildout seems to
> be a real pain for building distribution packages. it hardcodes absolute
> pathnames into scripts everywhere, etc.

I'm not sure, but maybe you'll be able to replace 'buildout' with any
of the incumbent successors, eg 'distribute' and/or eggbasket (no
advertising intended).

Another idea could be to defer the buildout process to the postinst
phase, so that shipping the 'raw' eggs and installing them at postinst
time could "work around", or alleviate, the hardcoded-paths issue.


Just my 0.02 cents - it's now been a while that I've actively looked at
such packaging tools.

> - we have to ship copies of dependency eggs within a cache dir inside
>   the source tarball.

Sounds about as good as it gets to me. Otherwise, offline installation
will not be possible.

> - this egg-cache can be used by adding download-cache and
>   install-from-cache options into buildout.cfg

Right.

> - all eggs are installed into eggs/ subdir by default. i don't like the
>   idea of installing this subdir within the zope2.12 package, but don't
>   see another solution either yet. (/usr/lib/zope2.12/python/eggs)?

The latter sounds better to me, if re-using these eggs should be
possible. I also wonder how to individually upgrade them, in case of a
problem (eg. a CVE).

> - absolut pathnames are hardcoded into bin/runzope, bin/zopepy, etc.

There's imho not much one can do to work around that. For me
personally, I recommend and use appropriate virtualenv-s for such
purposes to avoid cluttering the system. But of course, this completely
bypasses all FHS issues and, at the same time, prevents all kinds of
re-use or other system integration, too.


-- 
Kind regards,
--Toni++


Reply to: