Hi,
is there any initiative to share a common package format between conda and
pip? They look very similar.
Thanks
--
Distutils-SIG mailing list -- distutils-sig@python.org
To unsubscribe send an email to distutils-sig-le...@python.org
Rpm uses fewer requirements tags like Requires: and BuildRequires:
(the vastly common ones) plus other less frequently used like PreReq:
Provides: Conflicts: BuildConflicts: BuildPreReq: etc.
The BuildConflicts: I never seen a user case for it personally, the
Provides: and Conflicts: on
Because the version number is just more complicated? The details have
been ...
Nope, the whole point is it shouldn't. If that has to be enforced why
adding marketing alert to it? Why choosing something complex over
something simple?
In the correct world (mine where unicorns live freely) I
The distinction is useful in the life cycle context: an application
could depend on newer/older libraries than the one installed on the
system.
django-admin is an application from this life-cycle point of view.
Django is distributed as an application that contains its own library
(the
Please consider a user scenario quite common: the use of DESTDIR while
planning ahead for path resolution.
Linux distro use DESTDIR (and I believe autoconf-related things) uses
this env variable to set an alternative root, so:
prefix=/usr
sysconfdir=/etc
DESTDIR=/foo/bar
- bindir (if
Absolute path do make some sense in different contexts.
For example a server (system wide installed) as administrator I'm
expecting my config files to be under /etc.
As user (personal) I'm expecting my config files (for the same
application) could be under ~/.somewhere
A in-between could
in one place).
Funny enough distutils (the old dead horse) does it all except point 2:
that is my reason to clean up the code. I've just seen py3k distutils
but it would be worth a back port to py2k.
Thanks
Nick Coghlan wrote:
On Fri, Dec 14, 2012 at 10:10 AM, Antonio Cavallo
a.cava
It is not that complex... What's ahead is even more complex.
Lennart Regebro wrote:
On Fri, Dec 14, 2012 at 9:49 AM, Antonio Cavallo
a.cava...@cavallinux.eu wrote:
My requirements would quite simple:
2. cross compiling
That is *not* a simple requirement.
//Lennart
I'll have a look into distutils2, I tough it was (another) dead end.
I every case my target is py2k (2.7.x) and I've no case for
transitioning to py3k (too much risk).
Lennart Regebro wrote:
On Mon, Dec 10, 2012 at 8:22 AM, Antonio Cavallo
a.cava...@cavallinux.eu wrote:
Hi,
I wonder
Just come to my mind data test related to a package would be a natural
candidate:
mypack
|- __init__.py
|- test
|- __init__.py
|- test0.py
|- data
|- data.for.test0.dat
It is natural deploying them as part of an installer file.
I don't see why
On 5 Oct 2012, at 20:28, Stanley A. Klein wrote:
I assume that by an installer you mean the combination of package
building (done by e.g., rpmbuild) and installation (done by e.g., rpm or
yum).
Hi,
I think you've hit the jackpot here…
Here few lesson learnt using rpm and python at fairly
On 16 Mar 2011, at 12:47, Martin v. Löwis wrote:
Am 16.03.11 08:38, schrieb a.cava...@cavallinux.eu:
Hi,
please have a look into my little project:
http://pyvm.sf.net
This redirects me to
http://cclimited.webfactional.com/
Not sure whether it's the right page, if it is,
I'm
in the easy_xxx style).
I have done some work with it in the recent past if somebody is interested:
http://pyvm.sf.net
Regards,
Antonio Cavallo
On Thu, Jun 3, 2010 at 8:38 AM, Barry Warsaw ba...@python.org wrote:
So at the end, the end user would chose an installer that is
compatible
The PyPI discussions seem to be tending toward mixing the window dressing
with the framing, to use a building analogy, and what that will result in is
a weak frame and ugly windows. A building that slowly (or quickly) falls
down under its own weight, and looks bad doing it.
I think
Finally somebody had few doubts about CPAN...please have a look ti a
just-posted article on slashdot.
That mess is CPAN was my original reason to discard perl in first (and
switching to python): no two installed perl are ever the same. No way to
reliably reproduce the same environment and no
system like that
for that matter): there're are ALREADY platform standards, please
don't ignore them.
Regards,
Antonio Cavallo
PS. Why is that difficult a parallel install of packages under
site-packages/mypackage/X.Y.Z enforcing the X.Y.Z numbering?
Have I miss something? Am I too naive
SuSE runs a build service for free and support automatic rebuild of
packages from sources:
https://build.opensuse.org
For anyone interested you can find the lates svn python snapshot under:
http://download.opensuse.org/repositories/home:/cavallo71:/python-opt/
Each subdirectory (CentOS_5,
On Mon, Apr 20, 2009 at 6:04 PM, P.J. Eby p...@telecommunity.com wrote:
At 06:31 PM 4/20/2009 +0200, Lennart Regebro wrote:
Let me reformulate that:
Because that's the one that generates the metadata setuptools needs to
run,
test itself, etc.
Why do I need setuptools to do that? Why is
And, as I frequently run into walls that make me thing setuptools
should be completely ignored, and then after fiddling about quite a
bit, find a way around it, and then run into the next wall, etc, etc,
etc. And these walls are getting more and more frequent... I'm
beginning to think that
to be changed at some point;))
Let me know if this sounds a good idea,
Regards,
Antonio Cavallo
I'm packaging python for linux in a separate deirectory and I needed
to be completely system trasnparent,
On Thu, Apr 9, 2009 at 8:54 PM, Trent Mick tre...@activestate.com wrote:
Paul Moore
Hi,
I might be late and I haven't been to pycon but I've noted in this pep 345:
It is an attempt to re-invent the rpm spec file?
In this case how would you plan to integrate with the rpms dependecies?
Let me provide an usage scenario for packaging a generic rpm (foobar
from now on)
depending on
rpm(build) is a build tool, doens't deal with source distribution (but
it generates srpms
from the build sources).
There's a mild autodetection in rpmbuild when used in a restricted environment:
it detects installed but unpackaged files under $RPM_BUILD_ROOT.
It fails apart when used to build
(it come to my mind perforce): they
hold meta data into a remote server.
Regards,
Antonio Cavallo
Could we in this discussion, instead of making fuzzy general
statements explain exactly what the problems are?
___
Distutils-SIG maillist - Distutils
23 matches
Mail list logo
