blob: 02fb3a2b60fd7df7121aef865d62c1aadae60928 (
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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] rootcerts - $arch dependant noarch package?
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20rootcerts%20-%20%24arch%20dependant%20noarch%20package%3F&In-Reply-To=%3C201212132140.07150.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="020779.html">
<LINK REL="Next" HREF="020782.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] rootcerts - $arch dependant noarch package?</H1>
<B>Johnny A. Solbu</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20rootcerts%20-%20%24arch%20dependant%20noarch%20package%3F&In-Reply-To=%3C201212132140.07150.cooker%40solbu.net%3E"
TITLE="[Mageia-dev] rootcerts - $arch dependant noarch package?">cooker at solbu.net
</A><BR>
<I>Thu Dec 13 21:40:02 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="020779.html">[Mageia-dev] service dm restart go on tty3
</A></li>
<LI>Next message: <A HREF="020782.html">[Mageia-dev] [changelog] [RPM] cauldron core/release youri-check-0.10.2-2.mga3
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#20781">[ date ]</a>
<a href="thread.html#20781">[ thread ]</a>
<a href="subject.html#20781">[ subject ]</a>
<a href="author.html#20781">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Hi.
In our enviroment we are shipping our own local CA certificate on the machines. In order to learn how to do that properly, I looked at the rootcerts package.
In doing that I noticed that the rootcerts package is architecture dependant, as in it builds i586 and x86_64 packages, and not noarch. Yet there is no compiling involved and no binary files shipped, that I can detect, that would warrant an architecture dependant packaging.
So why isn't this a noarch package?
After all, it's just a set of certificate files.
--
Johnny A. Solbu
PGP key ID: 0xFA687324
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/mageia-dev/attachments/20121213/203b4ec0/attachment.asc>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="020779.html">[Mageia-dev] service dm restart go on tty3
</A></li>
<LI>Next message: <A HREF="020782.html">[Mageia-dev] [changelog] [RPM] cauldron core/release youri-check-0.10.2-2.mga3
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#20781">[ date ]</a>
<a href="thread.html#20781">[ thread ]</a>
<a href="subject.html#20781">[ subject ]</a>
<a href="author.html#20781">[ 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>
|
