lp its maintainer change it according to your
requirements to sponsorship requests, and probably integrate it into
nm.debian.org, too.
--
Dmitry Borodaenko
r change it according to your
requirements to sponsorship requests, and probably integrate it into
nm.debian.org, too.
--
Dmitry Borodaenko
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ons, and in
this case the arch-dep/indep criteria serves more to compicate things
than to make it more clear and consistent.
--
Dmitry Borodaenko
ore clear cut.
SL> Finally, i don't know, but are they all that much people really
SL> using /usr/share shared between different arches ?
At least that is usage that FHS refers to, and the only practical effect
of such division aside from abstract consistency.
SL> Does dpkg/apt even allow this to work without breaking all kind of
SL> things ?
AFAIK yes, but I'm too lazy to prove this :)
--
Dmitry Borodaenko
ons, and in
this case the arch-dep/indep criteria serves more to compicate things
than to make it more clear and consistent.
--
Dmitry Borodaenko
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Debian except Alicq are Ruby libraries :), nor in "arch-indep to
share" part: aside from common sense "lib is for libraries", in another
sub-thread it was already mentioned that even interpreted libraries are
not always "arch-indep".
--
Dmitry Borodaenko
ore clear cut.
SL> Finally, i don't know, but are they all that much people really
SL> using /usr/share shared between different arches ?
At least that is usage that FHS refers to, and the only practical effect
of such division aside from abstract consistency.
SL> Does dpkg/apt
Debian except Alicq are Ruby libraries :), nor in "arch-indep to
share" part: aside from common sense "lib is for libraries", in another
sub-thread it was already mentioned that even interpreted libraries are
not always "arch-indep".
--
Dmitry Borodaenko
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
thon stores everything in /usr/lib, again as a
SL> practical concession to the fact that upstream installation
SL> directories don't make it easy to use separate paths for
SL> arch-independent and arch-dependent objects.
Doesn't apply to Ruby.
--
Dmitry Borodaenko
le for some architectures, as is
the case with Alicq: it depends on tcl8.3 which is not available on Hurd
and SH. Not to mention Java "portability": we had problems porting Java
applications between Windows and Linux on i386 alone, I can imagine what
we'd encouter had we had to support MIPS.
--
Dmitry Borodaenko
thon stores everything in /usr/lib, again as a
SL> practical concession to the fact that upstream installation
SL> directories don't make it easy to use separate paths for
SL> arch-independent and arch-dependent objects.
Doesn't apply to Ruby.
--
Dmitry Borodaenko
--
T
le for some architectures, as is
the case with Alicq: it depends on tcl8.3 which is not available on Hurd
and SH. Not to mention Java "portability": we had problems porting Java
applications between Windows and Linux on i386 alone, I can imagine what
we'd encouter had we had to suppo
an interpreted language policies aren't consistent
on this issue, and whichever way I go, I end up inconsistent either with
Java and Emacs (/usr/share) or with Perl (/usr/share and /usr/lib) or
with Python, Ruby and Tcl (/usr/lib).
--
Dmitry Borodaenko
t part of such libaries into
/usr/lib (as is the case with Perl modules), and adding /usr/share to
the mix adds complexity necessity of which is questionable.
--
Dmitry Borodaenko
an interpreted language policies aren't consistent
on this issue, and whichever way I go, I end up inconsistent either with
Java and Emacs (/usr/share) or with Perl (/usr/share and /usr/lib) or
with Python, Ruby and Tcl (/usr/lib).
--
Dmitry Borodaenko
--
To UNSUBSCRIBE, email to [EMAIL PROTEC
t part of such libaries into
/usr/lib (as is the case with Perl modules), and adding /usr/share to
the mix adds complexity necessity of which is questionable.
--
Dmitry Borodaenko
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
is it really lacking precision about
modules and libraries for interpreted languages? Was this problem
discussed before?
--
Dmitry Borodaenko
is it really lacking precision about
modules and libraries for interpreted languages? Was this problem
discussed before?
--
Dmitry Borodaenko
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
n `build-indep' should be
added to the list of targets in the definition of Build-*-Indep, with
proper comments added to debian/rules section.
Can someone think about it? I haven't had a good sleep for two nights,
so I am not sure if I am thinking straight right now. Sorry ;)
--
Dmitry Borodaenko
n `build-indep' should be
added to the list of targets in the definition of Build-*-Indep, with
proper comments added to debian/rules section.
Can someone think about it? I haven't had a good sleep for two nights,
so I am not sure if I am thinking straight right now. Sorry ;)
--
Dmitry Borodaenko
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
20 matches
Mail list logo
