1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
|
<br><br><div class="gmail_quote">On Wed, Mar 6, 2013 at 8:44 AM, Guillaume Rousse <span dir="ltr"><<a href="mailto:guillomovitch@gmail.com" target="_blank">guillomovitch@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Le 06/03/2013 00:50, Reinout van Schouwen a écrit :<div><div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
The Dutch tax service makes life difficult for (64-bit) Mageia users<br>
because the tax filing program expects the i586 versions of libxext6 and<br>
libsm6 to be around.<br>
<br>
The tax service claim on their web site that Ubuntu 12.x and Linux Mint<br>
13 are supported. Could it be that they have these libraries<br>
preinstalled on 64 bit platforms?<br>
<br>
Would it be possible to provide some kind of stub package that downloads<br>
the program with the required dependencies, like Arch does? (<br>
<a href="https://aur.archlinux.org/packages/belastingdienst-ib2012/" target="_blank">https://aur.archlinux.org/<u></u>packages/belastingdienst-<u></u>ib2012/</a> )<br>
</blockquote></div></div>
Most binary-only i586 programs expects additional 32 bits libraires dependencies: skype, for instance. On a pure 64 bits systems, these libraries won't be installed, and they won't even be available directly, as long as 32 bits additional package sources are not configured...<br>
</blockquote><div><br></div><div>I think we configure the 32 bits media by default</div><div>Having a 32 bits package installing this app and having the proper dependencies would make sense</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I'm effraid than endlessly adding 32bits dependencies on our 64 bits packages, such as we did with pulseaudio for skype case, or adding 'stub' packages here, won't scale indefinitly to match every piece of softwares we can't distribute ourselves. First, they are exceptions to our 'self-containment' package sources policy... Second, dependencies won't adress the package source configuration issue.<br>
<br>
So, what about adressing end users intelligence, and document all those issues on a central 'compatibility' page on our wiki, instead of relying on such kind of hacks ?<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
BOFH excuse #155:<br>
<br>
Dumb terminal<br>
</font></span></blockquote></div><br>
|
