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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Teamviewer and X86_64 build . . .
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Teamviewer%20and%20X86_64%20build%20.%20.%20.&In-Reply-To=%3CCAPn0va6v0ud0RAW03hnpdsEKs0GpK%2BZ%3D46GCmobjv4Tt1Nhegg%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="009956.html">
<LINK REL="Next" HREF="009960.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Teamviewer and X86_64 build . . .</H1>
<B>Donald Stewart</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Teamviewer%20and%20X86_64%20build%20.%20.%20.&In-Reply-To=%3CCAPn0va6v0ud0RAW03hnpdsEKs0GpK%2BZ%3D46GCmobjv4Tt1Nhegg%40mail.gmail.com%3E"
TITLE="[Mageia-dev] Teamviewer and X86_64 build . . .">watersnowrock at gmail.com
</A><BR>
<I>Tue Nov 29 15:49:07 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="009956.html">[Mageia-dev] Teamviewer and X86_64 build . . .
</A></li>
<LI>Next message: <A HREF="009960.html">[Mageia-dev] Teamviewer and X86_64 build . . .
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9957">[ date ]</a>
<a href="thread.html#9957">[ thread ]</a>
<a href="subject.html#9957">[ subject ]</a>
<a href="author.html#9957">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 29 November 2011 14:23, Olav Vitters <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">olav at vitters.nl</A>> wrote:
><i> On Tue, Nov 29, 2011 at 11:43:30AM +0000, Donald Stewart wrote:
</I>>><i> But, as said earlier, this isn't really something that we can do
</I>>><i> sustainable so......
</I>><i>
</I>><i> Could do it on a best effort basis in a special meta package. I'd be
</I>><i> annoyed to complicate existing spec files with compatibility cruft, but
</I>><i> task-proprietary-compat-* subpackages seems fine to me.
</I>><i>
</I>><i> Might not work in all cases, in which case: too bad!
</I>><i>
</I>><i> Thinking of e.g.:
</I>><i> Provides: $FEDORA_THING
</I>><i> Requires: $OUR_THING
</I>><i>
</I>><i> --
</I>><i> Regards,
</I>><i> Olav
</I>
That way if a requires from the Fedora package changes, it is easier
to chase the changes needed for Mageia's packages, nice idea, however,
this would need to be documented so people know what it is and why its
getting pulled in. However, it would be a simpler thing to keep
updated and maintained that how-to's for each proprietary blob.
Schultz
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="009956.html">[Mageia-dev] Teamviewer and X86_64 build . . .
</A></li>
<LI>Next message: <A HREF="009960.html">[Mageia-dev] Teamviewer and X86_64 build . . .
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9957">[ date ]</a>
<a href="thread.html#9957">[ thread ]</a>
<a href="subject.html#9957">[ subject ]</a>
<a href="author.html#9957">[ 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>
|
