blob: 46560d14b02f51fb9ea6611c14c2849793bd3495 (
plain)
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] libproxy vs biarch & libexecdir
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20libproxy%20vs%20biarch%20%26%20libexecdir&In-Reply-To=%3Calpine.LMD.2.02.1106221202140.396%40zem.cjw.nep%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="005916.html">
<LINK REL="Next" HREF="005917.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] libproxy vs biarch & libexecdir</H1>
<B>Christiaan Welvaart</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20libproxy%20vs%20biarch%20%26%20libexecdir&In-Reply-To=%3Calpine.LMD.2.02.1106221202140.396%40zem.cjw.nep%3E"
TITLE="[Mageia-dev] libproxy vs biarch & libexecdir">cjw at daneel.dyndns.org
</A><BR>
<I>Wed Jun 22 17:49:20 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="005916.html">[Mageia-dev] gcc compiler error
</A></li>
<LI>Next message: <A HREF="005917.html">[Mageia-dev] libproxy vs biarch & libexecdir
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#5915">[ date ]</a>
<a href="thread.html#5915">[ thread ]</a>
<a href="subject.html#5915">[ subject ]</a>
<a href="author.html#5915">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>hi,
I'm trying to make sense of libproxy packaging. It consists of a regular
library and several modules. Currently, the library follows policy but the
module packages are named libproxy-foo, so they have the same name on x86
and x86-64:
i586 x86-64 description
==========================================================
libproxy1 lib64proxy1 main library
libproxy-gnome libproxy-gnome gnome proxy config support
libproxy-webkit libproxy-webkit webkit pacrunner (?)
etc.
- modules are in /usr/lib(64)/libproxy/%{version}/modules/
- libproxy-gnome also has a binary /usr/lib(64)/pxgconf (in 0.4.6 for
gnome2) or /usr/lib(64)/pxgsettings (in 0.4.7 for gnome3).
This looks wrong because:
- on a biarch system, it is not possible to have e.g. gnome3 settings
support for both archs
- the helper app (?) pxgsettings is put in libexecdir by upstream, so
IMHO it should be in /usr/lib or /usr/libexec, not %{_libdir} which
%{_libexecdir} expands to.
The specfile I have locally changes this to:
i586 x86-64 change
================================================================
libproxy1 lib64proxy1 same
libproxy-gnome lib64proxy-gnome biarch support
libproxy-webkit lib64proxy-webkit biarch support
libproxy-gxsettings libproxy-gxsettings new pkg
etc.
What should dependencies on these modules look like:
Requires: %mklibname proxy-gnome ?
Christiaan
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="005916.html">[Mageia-dev] gcc compiler error
</A></li>
<LI>Next message: <A HREF="005917.html">[Mageia-dev] libproxy vs biarch & libexecdir
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#5915">[ date ]</a>
<a href="thread.html#5915">[ thread ]</a>
<a href="subject.html#5915">[ subject ]</a>
<a href="author.html#5915">[ 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>
|
