blob: fc6779b2afebfe295a8f2717a85af111701d5442 (
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
|
<!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=%3C4ED5D1FD.2060205%40laposte.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="009961.html">
<LINK REL="Next" HREF="009947.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Teamviewer and X86_64 build . . .</H1>
<B>andre999</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=%3C4ED5D1FD.2060205%40laposte.net%3E"
TITLE="[Mageia-dev] Teamviewer and X86_64 build . . .">andre999mga at laposte.net
</A><BR>
<I>Wed Nov 30 07:49:33 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="009961.html">[Mageia-dev] Teamviewer and X86_64 build . . .
</A></li>
<LI>Next message: <A HREF="009947.html">[Mageia-dev] Teamviewer and X86_64 build . . .
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9990">[ date ]</a>
<a href="thread.html#9990">[ thread ]</a>
<a href="subject.html#9990">[ subject ]</a>
<a href="author.html#9990">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Olav Vitters a écrit :
><i> On Tue, Nov 29, 2011 at 11:43:30AM +0000, Donald Stewart wrote:
</I>><i>
</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've been thinking of something like for the RPM categories.
It wouldn't have to be focused on Redhat/Fedora only, as Suse seems to
differ as well.
Maybe something that could massage the installable rpm files, so any
user could adjust whatever rpm, even without the srpm.
--
André
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="009961.html">[Mageia-dev] Teamviewer and X86_64 build . . .
</A></li>
<LI>Next message: <A HREF="009947.html">[Mageia-dev] Teamviewer and X86_64 build . . .
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9990">[ date ]</a>
<a href="thread.html#9990">[ thread ]</a>
<a href="subject.html#9990">[ subject ]</a>
<a href="author.html#9990">[ 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>
|