Goswin von Brederlow goswin-...@web.de (29/07/2009):
Thoughts from the maintainer?
You may want to read #468209, which is kind of related.
Mraw,
KiBi.
signature.asc
Description: Digital signature
Charles Plessy ple...@debian.org (30/07/2009):
I have three questions about Multi-arch:
1) […]
2) […]
3) Where is the third question? :)
Mraw,
KiBi.
signature.asc
Description: Digital signature
Charles Plessy, le Thu 30 Jul 2009 13:13:59 +0900, a écrit :
1) What is the advantage of adding a new field over simply using something
like
‘Arch: multi’?
Err, I believe it makes sense to mark an i386/amd64-only library as
multiarch-capable.
Samuel
--
To UNSUBSCRIBE, email to
Zitat von sthiba...@debian.org:
My first thought was Err. Won't moving all the shared libs into a
different location kinda screw things up? And then I looked, and found
| == /etc/ld.so.conf.d/x86_64-linux-gnu.conf ==
Yes, but however pkg-config won't yet find things in
Hendrik Sattler, le Thu 30 Jul 2009 10:35:38 +0200, a écrit :
Zitat von sthiba...@debian.org:
My first thought was Err. Won't moving all the shared libs into a
different location kinda screw things up? And then I looked, and found
| == /etc/ld.so.conf.d/x86_64-linux-gnu.conf ==
On Wed, 29 Jul 2009, Goswin von Brederlow wrote:
However, you *can* share the same .mo files on each platform, since the
gettext code copes with endianness issues at runtime if need be.
So we would have to define a default endianness for creating such
files. A patch to gettext to create
Steve Langasek vor...@debian.org writes:
On Wed, Jul 29, 2009 at 07:38:22PM -0500, Peter Samuelson wrote:
We have mostly settled the /usr/share/locale question, and apparently
/usr/share/doc is a special exception anyway
No, it is not. The ubiquity of /usr/share/doc provides the
Charles Plessy ple...@debian.org writes:
Le Wed, Jul 29, 2009 at 03:57:31PM +0200, Goswin von Brederlow a écrit :
I got some good feedback from my previous Introduction to multiarch
post and some good questions. I'm singling out Manoj Srivastava here
because he was the most recent to ask
On Thu, Jul 30, 2009 at 11:04:46AM +0200, Samuel Thibault wrote:
Yes, but however pkg-config won't yet find things in
/usr/lib/x86_64-linux-gnu/pkgconfig, so take care of putting .pc files
in /usr/lib/pkgconfig.
$ pkg-config --list-all --debug
[...]
Cannot open directory
]]
| My first thought was Err. Won't moving all the shared libs into a
| different location kinda screw things up? And then I looked, and found
|
|| == /etc/ld.so.conf.d/x86_64-linux-gnu.conf ==
|
| Yes, but however pkg-config won't yet find things in
|
]] Gabor Gombas
| Later pkg-config should be extended to have an --arch command-line
| option (or env. variable) that is substituted into the default search
| path at run time rather than at build time, but that can wait.
This has been considered before, and I'm not yet convinced it's a better
, on irc is
was just 3 lines. But half the mail are 2 two example patches. So here
we go:
Introduction to multiarch: What maintainers must do
===
To begin with there are 5 cases to consider: (in order of complexity)
1) Architecture: all package
2
Hi,
small add on.
Any package in debian can be multiarchified at any time. You do not
have to wait for all your depends to be multiarchified or notifiy your
reverse depends when you are ready. The state of your depends will
only matter when someone actualy does a multiarch installation and
On Wed, Jul 29 2009, Goswin von Brederlow wrote:
Hi,
small add on.
Any package in debian can be multiarchified at any time. You do not
have to wait for all your depends to be multiarchified or notifiy your
reverse depends when you are ready. The state of your depends will
only matter when
My first thought was Err. Won't moving all the shared libs into a
different location kinda screw things up? And then I looked, and found
| == /etc/ld.so.conf.d/x86_64-linux-gnu.conf ==
Yes, but however pkg-config won't yet find things in
/usr/lib/x86_64-linux-gnu/pkgconfig, so take
Manoj Srivastava sriva...@debian.org writes:
On Wed, Jul 29 2009, Goswin von Brederlow wrote:
Hi,
small add on.
Any package in debian can be multiarchified at any time. You do not
have to wait for all your depends to be multiarchified or notifiy your
reverse depends when you are ready.
Thanks for this excellent post, Goswin.
[Goswin von Brederlow]
3) Library package
--
a) Follow Policy 8.2 (MUST directive)
No conffiles, no binaries in the library package, no shared files
(/usr/share/doc/package/ is excempt and dpkg will handle that).
Policy
On Wed, Jul 29, 2009 at 11:53:37AM -0500, Peter Samuelson wrote:
Thanks for this excellent post, Goswin.
[Goswin von Brederlow]
3) Library package
--
a) Follow Policy 8.2 (MUST directive)
No conffiles, no binaries in the library package, no shared files
sthiba...@debian.org writes:
My first thought was Err. Won't moving all the shared libs into a
different location kinda screw things up? And then I looked, and found
| == /etc/ld.so.conf.d/x86_64-linux-gnu.conf ==
Yes, but however pkg-config won't yet find things in
On Wed, Jul 29, 2009 at 11:09:32AM -0500, Manoj Srivastava wrote:
My first thought was Err. Won't moving all the shared libs into
a different location kinda screw things up? And then I looked, and
found
,
| == /etc/ld.so.conf.d/x86_64-linux-gnu.conf ==
| # Multiarch support
Steve Langasek, le Wed 29 Jul 2009 19:01:57 +0200, a écrit :
the only requirement is that any files shipped there are identical
between packages of the same version for multiple architectures.
That's however not true for .mo files, for endianness, typically.
Samuel
--
To UNSUBSCRIBE, email
Goswin von Brederlow, le Wed 29 Jul 2009 19:09:59 +0200, a écrit :
sthiba...@debian.org writes:
My first thought was Err. Won't moving all the shared libs into a
different location kinda screw things up? And then I looked, and found
| == /etc/ld.so.conf.d/x86_64-linux-gnu.conf ==
Steve Langasek, le Wed 29 Jul 2009 19:01:57 +0200, a écrit :
the only requirement is that any files shipped there are identical
between packages of the same version for multiple architectures.
[Samuel Thibault]
That's however not true for .mo files, for endianness, typically.
So what does
On Wed, Jul 29, 2009 at 01:41:20PM -0500, Peter Samuelson wrote:
Steve Langasek, le Wed 29 Jul 2009 19:01:57 +0200, a écrit :
the only requirement is that any files shipped there are identical
between packages of the same version for multiple architectures.
[Samuel Thibault]
That's
Peter Samuelson, le Wed 29 Jul 2009 13:41:20 -0500, a écrit :
Steve Langasek, le Wed 29 Jul 2009 19:01:57 +0200, a écrit :
the only requirement is that any files shipped there are identical
between packages of the same version for multiple architectures.
[Samuel Thibault]
That's
Samuel Thibault sthiba...@debian.org writes:
Goswin von Brederlow, le Wed 29 Jul 2009 19:09:59 +0200, a écrit :
sthiba...@debian.org writes:
My first thought was Err. Won't moving all the shared libs into a
different location kinda screw things up? And then I looked, and found
|
Samuel Thibault sthiba...@debian.org writes:
Steve Langasek, le Wed 29 Jul 2009 19:01:57 +0200, a écrit :
the only requirement is that any files shipped there are identical
between packages of the same version for multiple architectures.
That's however not true for .mo files, for endianness,
Goswin von Brederlow goswin-...@web.de writes:
Any of the lintian people reading this?
Yes, but only very intermittantly between other things since I'm on
semi-vacation this week.
Could we create a check for *.pc files that they are in the right
place and right package in anticipation of
Henning Glawe gla...@debian.org writes:
On Wed, Jul 29, 2009 at 11:09:32AM -0500, Manoj Srivastava wrote:
My first thought was Err. Won't moving all the shared libs into
a different location kinda screw things up? And then I looked, and
found
,
| ==
Hi gettext,
while talking about multiarch the issue was raised that
/usr/share/locale/*/*package.mo
is not identical across all architectures as multiarch would require.
Russ Allbery r...@debian.org writes:
Samuel Thibault sthiba...@debian.org writes:
Steve Langasek, le Wed 29 Jul 2009
Russ Allbery r...@debian.org writes:
Goswin von Brederlow goswin-...@web.de writes:
Any of the lintian people reading this?
Yes, but only very intermittantly between other things since I'm on
semi-vacation this week.
Could we create a check for *.pc files that they are in the right
place
On Wed, Jul 29, 2009 at 11:33:51PM +0200, Goswin von Brederlow wrote:
Henning Glawe gla...@debian.org writes:
On Wed, Jul 29, 2009 at 11:09:32AM -0500, Manoj Srivastava wrote:
My first thought was Err. Won't moving all the shared libs into
a different location kinda screw things
[Goswin von Brederlow]
3) Library package
--
a) Follow Policy 8.2 (MUST directive)
No conffiles, no binaries in the library package, no shared files
(/usr/share/doc/package/ is excempt and dpkg will handle that).
We have mostly settled the /usr/share/locale
On Wed, Jul 29, 2009 at 07:38:22PM -0500, Peter Samuelson wrote:
We have mostly settled the /usr/share/locale question, and apparently
/usr/share/doc is a special exception anyway
No, it is not. The ubiquity of /usr/share/doc provides the *rationale* for
multiarch handling /usr/share in a
Le Wed, Jul 29, 2009 at 03:57:31PM +0200, Goswin von Brederlow a écrit :
I got some good feedback from my previous Introduction to multiarch
post and some good questions. I'm singling out Manoj Srivastava here
because he was the most recent to ask this on irc but there where
others with the
35 matches
Mail list logo
