On 11/05/15 08:03, Ole Streicher wrote:
> What is the rationale between having all this in /usr/lib?
Conversely, it might be informative to consider the rationale for
/usr/lib and /usr/share being separate:
"""
This hierarchy is intended to be shareable among all architecture
platforms of a given
Charles Plessy writes:
> indeed, this is a recent change in the Policy (see
> bugs.debian.org/741304).
Putting pure python packages (Architecture: all) into /usr/lib is IMO
still not coved by the Debian Policy.
> Probably Lintian is lagging behind. Maybe somebody can ping bug #415558 ?
I'll do
Matthias Klose writes:
> The FHS never talks about putting *code* into /usr/share. So pybuild
> is right from my point of view to put it in /usr/lib.
I think the Debian Policy is quite clear here:
| [...] However, when a directory is entirely composed of
| architecture-independent files, it shou
On 05/11/2015 09:03 AM, Ole Streicher wrote:
> Ben Finney writes:
>> Ole Streicher writes:
>> Installing the non-program files to ‘/usr/share/foopackage/images/’ (for
>> example) is simple enough, using ‘dh_install’.
>
> I am using pybuild, and I am wondering why it doesn't do this
> automatical
Le Mon, May 11, 2015 at 09:03:53AM +0200, Ole Streicher a écrit :
>
> The Debian Policy [4] states (9.1.1):
>
> | 1. The FHS requirement that architecture-independent application-
> | specific static files be located in /usr/share is relaxed to a
> | suggestion. In particular, a subdirectory of /
Ole Streicher writes:
> Ben Finney writes:
> > Ole Streicher writes:
> > Installing the non-program files to ‘/usr/share/foopackage/images/’ (for
> > example) is simple enough, using ‘dh_install’.
>
> I am using pybuild, and I am wondering why it doesn't do this
> automatically (maybe with some
Ben Finney writes:
> Ole Streicher writes:
> Installing the non-program files to ‘/usr/share/foopackage/images/’ (for
> example) is simple enough, using ‘dh_install’.
I am using pybuild, and I am wondering why it doesn't do this
automatically (maybe with some help)?
Generally: pybuild seem to i
On 05/11/2015 04:08 AM, Ben Finney wrote:
> "Paul R. Tagliamonte" writes:
>
>> That or symlink them in from /usr/share ;)
>
> Yes, that works too (and I've done it in my packages):
>
> Use ‘dh_install’ to install the non-program files to the correct
> location under ‘/usr/share/foopackage/’, an
"Paul R. Tagliamonte" writes:
> That or symlink them in from /usr/share ;)
Yes, that works too (and I've done it in my packages):
Use ‘dh_install’ to install the non-program files to the correct
location under ‘/usr/share/foopackage/’, and then create symlinks in the
program directories where t
That or symlink them in from /usr/share ;)
On May 10, 2015 7:43 PM, "Ben Finney" wrote:
> Ole Streicher writes:
>
> > some of the package I maintain (namely python-astropy), or want to
> > package, contain images within their python source directories. When
> > installed using the normal setup,
Ole Streicher writes:
> some of the package I maintain (namely python-astropy), or want to
> package, contain images within their python source directories. When
> installed using the normal setup, these images get installed in
> /usr/lib, leading to the lintian warning shown in the subject.
>
>
11 matches
Mail list logo
