zarb-ml/mageia-dev/2012-May/015805.html


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] Upgrade: Seamonkey 2.9.1
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Upgrade%3A%20Seamonkey%202.9.1&In-Reply-To=%3C201205241641.47207.cooker%40solbu.net%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="015824.html">
   <LINK REL="Next"  HREF="015806.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Upgrade: Seamonkey 2.9.1</H1>
    <B>Johnny A. Solbu</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Upgrade%3A%20Seamonkey%202.9.1&In-Reply-To=%3C201205241641.47207.cooker%40solbu.net%3E"
       TITLE="[Mageia-dev] Upgrade: Seamonkey 2.9.1">cooker at solbu.net
       </A><BR>
    <I>Thu May 24 16:41:43 CEST 2012</I>
    <P><UL>
        <LI>Previous message: <A HREF="015824.html">[Mageia-dev] Upgrade: Seamonkey 2.9.1
</A></li>
        <LI>Next message: <A HREF="015806.html">[Mageia-dev] Upgrade: Seamonkey 2.9.1
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#15805">[ date ]</a>
              <a href="thread.html#15805">[ thread ]</a>
              <a href="subject.html#15805">[ subject ]</a>
              <a href="author.html#15805">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>On Wednesday 23 May 2012 15:42, Eric Elena wrote:
&gt;<i> Now, what you have been waiting for, the files are available here:
</I>&gt;<i> <A HREF="http://voguemerry.com/seamonkey">http://voguemerry.com/seamonkey</A> 
</I>
May I suggest that you also do what I do, have a folder with the src.rpm packages. That way those who want can easily recompile the packages them selves, possibly on 64 bit systems.

If I understand FSF and the GPL correctly, it's not enough that you point to the upstream sourcecode repostitory. If you provide GPL software, you must also provide the sourcecode. And the easy way to do that is to provide the source rpm's. That way you don't forget any of the files required to build a package, as all required files will be in te src.rpm's. :-)=

-- 
Johnny A. Solbu
PGP key ID: 0xFA687324
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: &lt;/pipermail/mageia-dev/attachments/20120524/e85fe958/attachment.asc&gt;
</PRE>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="015824.html">[Mageia-dev] Upgrade: Seamonkey 2.9.1
</A></li>
	<LI>Next message: <A HREF="015806.html">[Mageia-dev] Upgrade: Seamonkey 2.9.1
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#15805">[ date ]</a>
              <a href="thread.html#15805">[ thread ]</a>
              <a href="subject.html#15805">[ subject ]</a>
              <a href="author.html#15805">[ 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>