Josselin Mouette <[EMAIL PROTECTED]> writes:
> Le jeudi 11 octobre 2007 à 10:50 +1000, Ben Finney a écrit :
> > The main reason I use distutils is to assist those people using
> > operating systems that *don't* have good package dependency
> > management, which seems to be the primary target marke
Le jeudi 11 octobre 2007 à 10:50 +1000, Ben Finney a écrit :
> The main reason I use distutils is to assist those people using
> operating systems that *don't* have good package dependency
> management, which seems to be the primary target market for
> setuptools.
This is a laudable goal, but not
Ben Finney <[EMAIL PROTECTED]> writes:
> The main reason I use distutils is to assist those people using
> operating systems that *don't* have good package dependency
> management, which seems to be the primary target market for
> setuptools.
This should, of course, read "The main reason I use se
Bernd, please follow the Debian mailing list code of conduct
http://www.debian.org/MailingLists#codeofconduct>, in particular
by *not* sending personal copies of messages that are also sent to the
list.
Also, please preserve attribution lines so we can keep track of who
wrote what quoted material.
>
> I'm confused, then. How does this fit with the implication (in the
> above quoted teset) that upstream should have "thought of [changing
> the location of the modules]"? If downstream hackery is required, I
> don't see what upstream is expected to have done.
>
>
That is imho nothing ups
(Please preserve attribution lines on quoted material. I don't know
who wrote what in the following.)
Josselin Mouette <[EMAIL PROTECTED]> writes:
> Le lundi 01 octobre 2007 à 23:56 +1000, Ben Finney a écrit :
> > > > Hmm. I am hoping that "modify the programs [to add an absolute
> > > > path to
Le lundi 01 octobre 2007 à 23:56 +1000, Ben Finney a écrit :
> > > Hmm. I am hoping that "modify the programs [to add an absolute
> > > path to the search path]" is not a necessary part of this.
> >
> > If upstream hasn't thought of it, it is. You only need to add one
> > line in the program, befo
> As an example, here's a Python package I'm trying to get packaged for
> Debian. (I am the upstream author of this one, but I'm interested in a
> solution that *doesn't* involve significant changes to the upstream
> code.)
>
> http://cheeseshop.python.org/pypi/gracie/>
The first thing I'd d
Ben Finney <[EMAIL PROTECTED]> writes:
> How can I best conform to the [Debian policy for Python modules
> specific to a single package]?
As an example, here's a Python package I'm trying to get packaged for
Debian. (I am the upstream author of this one, but I'm interested in a
solution that *doe
Josselin Mouette <[EMAIL PROTECTED]> writes:
> Le lundi 01 octobre 2007 à 18:37 +1000, Ben Finney a écrit :
> > How can I use the tools available — distutils, setuptools,
> > debhelper — to install these package-specific modules to a
> > package-specific location, such that all the programs in the
Le lundi 01 octobre 2007 à 18:37 +1000, Ben Finney a écrit :
> > That would work if the files were shipped
> > in /usr/lib/python2.X/site-packages.
>
> That's where the distutils and setuptools place them by default,
> yes. I don't know what magic is required to put them elsewhere; that
> may be p
> If the policy recommends that packages be set up a particular way
> ("put package-specific modules in '/usr/share/package/'"), but the
> standard tools behave differently ("put all modules by default in
> '/usr/lib/pythonX.Y/site-packages/'"), then there's a step that needs
> to be taken to get
Bernd Zeimetz <[EMAIL PROTECTED]> writes:
> You shoul dupload your work somewhere, "teaching" you is almost
> impossible if one can't see what's wrong.
I'm not presenting something as "wrong". I'm asking for guidance on
how to do things right.
If the policy recommends that packages be set up a p
> That's where the distutils and setuptools place them by default,
> yes. I don't know what magic is required to put them elsewhere; that
> may be part of the answer, if someone can instruct me on how to do it.
You shoul dupload your work somewhere, "teaching" you is almost
impossible if one can'
Josselin Mouette <[EMAIL PROTECTED]> writes:
> Le lundi 01 octobre 2007 à 14:42 +1000, Ben Finney a écrit :
> > But the Python distutils and setuptools will install the modules
> > to /usr/lib/site-python/.
>
> Hrm, they shouldn't. With a default setup, public modules are
> shipped to /usr/lib/py
Le lundi 01 octobre 2007 à 14:42 +1000, Ben Finney a écrit :
> 3.1.1 Programs Shipping Private Modules
>
> A program using /usr/bin/python as interpreter can come up with
> private Python modules. These modules should be installed in
> /usr/share/module, or /usr/lib/module if the m
Howdy all,
The Debian Python Policy, chapter 3
http://www.debian.org/doc/packaging-manuals/python-policy/ch-programs.html>
says:
3.1.1 Programs Shipping Private Modules
A program using /usr/bin/python as interpreter can come up with
private Python modules. These modules should be ins
17 matches
Mail list logo
