I am not a debian guru, but just got a package to upstream and had similar
doubt.
For python packages, at least, this is my understanding of it. You may have
python libraries or python applications. Python libraries are placed in
"public" location, this means that the package will be accessible wi
On 06-Apr-12 23:26, Natalia Frydrych wrote:
Hi!
My name is Natalia Frydrych. This year, for the first time, I want to
take part in the Google Summer of Code.
My project proposal is available at:
http://wiki.debian.org/SummerOfCode2012/StudentApplications/NataliaFrydrych
I am going to write it
On Sunday, April 29, 2012 03:16:12 AM you wrote:
> I am not a debian guru, but just got a package to upstream and had similar
> doubt.
>
> For python packages, at least, this is my understanding of it. You may have
> python libraries or python applications. Python libraries are placed in
> "public
No need to mess with setup.py directly. Use dh_python2 to do the packaging
work for you, and rely on debian/rules to define the location of your
files. Read:
http://wiki.debian.org/Python/TransitionToDHPython2
On Monday, April 30, 2012, Paul Elliott
wrote:
> On Sunday, April 29, 2012 03:16:12 AM
Paul Elliott writes:
> My package uses a package that it makes public. What is the standard,
> established way to take that package private?
In the absence of better-informed answers (please, knowledgeable Debian
Python people, help us out with this information!):
The Debian Python Policy says
5 matches
Mail list logo
