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
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Dutch tax program dependencies
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Dutch%20tax%20program%20dependencies&In-Reply-To=%3CCAPGqOedcZ%2BNG0p5cfOqQrEFHheiGhuUuw-k2rWGSTE_731wXbg%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="023329.html">
<LINK REL="Next" HREF="023328.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Dutch tax program dependencies</H1>
<B>Reinout van Schouwen</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Dutch%20tax%20program%20dependencies&In-Reply-To=%3CCAPGqOedcZ%2BNG0p5cfOqQrEFHheiGhuUuw-k2rWGSTE_731wXbg%40mail.gmail.com%3E"
TITLE="[Mageia-dev] Dutch tax program dependencies">reinout at gmail.com
</A><BR>
<I>Sun Mar 10 14:34:00 CET 2013</I>
<P><UL>
<LI>Previous message: <A HREF="023329.html">[Mageia-dev] Dutch tax program dependencies
</A></li>
<LI>Next message: <A HREF="023328.html">[Mageia-dev] Dutch tax program dependencies
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#23394">[ date ]</a>
<a href="thread.html#23394">[ thread ]</a>
<a href="subject.html#23394">[ subject ]</a>
<a href="author.html#23394">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Yes Pascal, that would be great. Keeping in mind, of course, that a
mechanism (via updates?) to provide the equivalent packages for next
year's tax program would have to be in place, otherwise it would
hardly make sense.
Reinout
2013/3/6 Pascal Terjan <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">pterjan at gmail.com</A>>:
><i>
</I>><i>
</I>><i> On Wed, Mar 6, 2013 at 8:44 AM, Guillaume Rousse <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">guillomovitch at gmail.com</A>>
</I>><i> wrote:
</I>>><i>
</I>>><i> Le 06/03/2013 00:50, Reinout van Schouwen a écrit :
</I>>><i>
</I>>>><i> Hi all,
</I>>>><i>
</I>>>><i> The Dutch tax service makes life difficult for (64-bit) Mageia users
</I>>>><i> because the tax filing program expects the i586 versions of libxext6 and
</I>>>><i> libsm6 to be around.
</I>>>><i>
</I>>>><i> The tax service claim on their web site that Ubuntu 12.x and Linux Mint
</I>>>><i> 13 are supported. Could it be that they have these libraries
</I>>>><i> preinstalled on 64 bit platforms?
</I>>>><i>
</I>>>><i> Would it be possible to provide some kind of stub package that downloads
</I>>>><i> the program with the required dependencies, like Arch does? (
</I>>>><i> <A HREF="https://aur.archlinux.org/packages/belastingdienst-ib2012/">https://aur.archlinux.org/packages/belastingdienst-ib2012/</A> )
</I>>><i>
</I>>><i> Most binary-only i586 programs expects additional 32 bits libraires
</I>>><i> dependencies: skype, for instance. On a pure 64 bits systems, these
</I>>><i> libraries won't be installed, and they won't even be available directly, as
</I>>><i> long as 32 bits additional package sources are not configured...
</I>><i>
</I>><i>
</I>><i> I think we configure the 32 bits media by default
</I>><i> Having a 32 bits package installing this app and having the proper
</I>><i> dependencies would make sense
</I>><i>
</I>>><i>
</I>>><i> I'm effraid than endlessly adding 32bits dependencies on our 64 bits
</I>>><i> packages, such as we did with pulseaudio for skype case, or adding 'stub'
</I>>><i> packages here, won't scale indefinitly to match every piece of softwares we
</I>>><i> can't distribute ourselves. First, they are exceptions to our
</I>>><i> 'self-containment' package sources policy... Second, dependencies won't
</I>>><i> adress the package source configuration issue.
</I>>><i>
</I>>><i> So, what about adressing end users intelligence, and document all those
</I>>><i> issues on a central 'compatibility' page on our wiki, instead of relying on
</I>>><i> such kind of hacks ?
</I>>><i>
</I>>><i> --
</I>>><i> BOFH excuse #155:
</I>>><i>
</I>>><i> Dumb terminal
</I>><i>
</I>><i>
</I>
--
Reinout van Schouwen
<A HREF="http://vanschouwen.info/">http://vanschouwen.info/</A>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="023329.html">[Mageia-dev] Dutch tax program dependencies
</A></li>
<LI>Next message: <A HREF="023328.html">[Mageia-dev] Dutch tax program dependencies
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#23394">[ date ]</a>
<a href="thread.html#23394">[ thread ]</a>
<a href="subject.html#23394">[ subject ]</a>
<a href="author.html#23394">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
