Mikhail Gusarov wrote:
> ML> At least the packager will know that s3cmd will require ET for its
> ML> run.
>
> You have completely confused the *build* dependencies and *runtime*
> dependencies:
>
> Build-Depends: debhelper (>= 7), quilt (>= 0.40), python-all-dev (>= 2.3.5-11)
> Build-Depends-Indep: python-central (>= 0.6)
>
> Depends: python (>= 2.5) | python-elementtree, ${python:Depends}
This is what I have in RPM spec:
%if %{defined use_elementtree}
BuildRequires: python-elementtree
Requires: python-elementtree
%endif
%if %{defined use_python_xml}
BuildRequires: python-xml
Requires: python-xml
%endif
It indeed does install one sort-of-useless package during build but I
don't see any problem with that. The build is perhaps 1 second slower,
and that's about it.
The reason I prefer to have it in is to give a hint to the packager that
ET will be required in runtime. Packages are usualy built in a clean
environment but the packagers test them on their workstations. They may
already have ET installed and the test run will be just fine for them
and wouldn't realise they need an installation dependency for ET. If it
fails in clean build env it's more clear that something is wrong.
So, feel free to remove the check in Debian, but I'd better keep it in
the stock setup.py if you don't mind ;-)
Michal
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
S3tools-general mailing list
S3tools-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/s3tools-general
