From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-discuss/20110223/003766.html | 100 ++++++++++++++++++++++++++++ 1 file changed, 100 insertions(+) create mode 100644 zarb-ml/mageia-discuss/20110223/003766.html (limited to 'zarb-ml/mageia-discuss/20110223/003766.html') diff --git a/zarb-ml/mageia-discuss/20110223/003766.html b/zarb-ml/mageia-discuss/20110223/003766.html new file mode 100644 index 000000000..0bef0cb8c --- /dev/null +++ b/zarb-ml/mageia-discuss/20110223/003766.html @@ -0,0 +1,100 @@ + + + + [Mageia-discuss] Attention, please + + + + + + + + + +

[Mageia-discuss] Attention, please

+ nicolas vigier + boklm at mars-attacks.org +
+ Wed Feb 23 20:39:06 CET 2011 +

+
+ +
On Wed, 23 Feb 2011, André Machado wrote:
+
+> Well, more precisely, what do you have in mind ?
+> 
+> Currently, I'm thinking in two main goals:
+> 
+> I. Create a website where:
+> 
+>     a. we can promote RPM-based distros usage to general public;
+
+Why only RPM-based distros ?
+
+> II. Make agreement with main RPM distros to standardization:
+> 
+>     a. Standardize naming and versioning of packages
+>           Nowadays, it's common that, in one distro, a package be called
+>           'samba' and, in another, 'smb'. Thus, if we try install a
+>           package made for the first one in the second, we can break
+>           dependence tree. Standardizing the naming and the versioning
+>           would solve this issue. Comnpatibility with current distro
+>           versions could be achieved by dummy packages.
+> 
+>     b. Standardize file locations
+>           Even if you can install a package made for a distro to another
+>           without breaking the dependency tree, can occur in the
+>           application does not find the libraries or configuration files
+>           that need, being necessary to create symbolic links to them.
+>           Standardize the location of these files would solve the problem.
+>           Comnpatibility with current and old distro versions could be
+>           achieved by symlinks created automatically during install.
+> 
+>     c. Standardize init scripts
+>           By similar reasons.
+> 
+> Of course, this won't be easy, but let's intone this slogan: "Pack once, install
+> everywhere".
+
+It's already difficult to install a package from one release of a
+distribution on an other release of the same distribution, which usually
+have the same naming of packages, file locations and init scripts ...
+
+But why do you want to be able to do this ?
+
+
+ + + + +
+

+ +
+More information about the Mageia-discuss +mailing list
+ -- cgit v1.2.1