[Paul Elliott, 2012-05-01]
> I have a third question: what if my debian package had 2 or more private
> python packages?
--install-lib=/usr/share/foo/ (or /usr/lib/foo/)
where foo is binary package name
i.e.
/usr/share/foo/bar.py
/usr/share/foo/baz.py
or
/usr/lib/foo/bar.py
/usr/lib/foo/baz.so
/
[Paul Elliott, 2012-05-01]
> This worked as far as moving the python package openastromod
>
> > override_dh_auto_install:
> > dh_auto_install -- --install-lib /usr/share/openastromod
>
> I removed the "--install-scripts /usr/share/openastromod" because
> openastromod
> does not have any use
On Tuesday, May 01, 2012 03:14:13 PM Paul Elliott wrote:
> On Tuesday, May 01, 2012 04:15:41 AM Stefano Rivera wrote:
> > Hi Ben (2012.05.01_05:08:17_+0200)
> >
> > > What is the best *method* to do this, though? How to best use existing
> > > tools so as not to re-implement this boilerplate task
On Tuesday, May 01, 2012 04:15:41 AM Stefano Rivera wrote:
> Hi Ben (2012.05.01_05:08:17_+0200)
>
> > What is the best *method* to do this, though? How to best use existing
> > tools so as not to re-implement this boilerplate task every time such a
> > package comes along?
>
> The usual way to ma
On May 01, 2012, at 11:37 AM, Scott Kitterman wrote:
>On Tuesday, May 01, 2012 10:45:24 AM Barry Warsaw wrote:
>...
>> The ipaddr library is as well, though that might get the "provisional"
>> tag.
>...
>This is one I'll need to keep an eye on as ipaddr is packaged in dpmt as a
>seperate module
On Tuesday, May 01, 2012 10:45:24 AM Barry Warsaw wrote:
...
> The ipaddr library is as well, though that might get the "provisional"
> tag.
...
This is one I'll need to keep an eye on as ipaddr is packaged in dpmt as a
seperate module (maintained by me). Upstream has a separate release that's
I just wanted to make people aware of the upstream Python 3.3 schedule. 3.3
alpha 3 was tagged today and we're less than two months away from beta 1.
Georg Brandl (the 3.3 release manager) sent out this message today:
http://mail.python.org/pipermail/python-dev/2012-May/119157.html
PEP 398 cover
Hi Ben (2012.05.01_05:08:17_+0200)
> What is the best *method* to do this, though? How to best use existing
> tools so as not to re-implement this boilerplate task every time such a
> package comes along?
The usual way to make a package private is to do something like:
override_dh_auto_install:
8 matches
Mail list logo