diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20110121/002280.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20110121/002280.html | 113 |
1 files changed, 113 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110121/002280.html b/zarb-ml/mageia-dev/20110121/002280.html new file mode 100644 index 000000000..c6a595951 --- /dev/null +++ b/zarb-ml/mageia-dev/20110121/002280.html @@ -0,0 +1,113 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Java-Policy first draft published + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Java-Policy%20first%20draft%20published&In-Reply-To=%3C20110121011440.GD21938%40mars-attacks.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002285.html"> + <LINK REL="Next" HREF="002286.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Java-Policy first draft published</H1> + <B>nicolas vigier</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Java-Policy%20first%20draft%20published&In-Reply-To=%3C20110121011440.GD21938%40mars-attacks.org%3E" + TITLE="[Mageia-dev] Java-Policy first draft published">boklm at mars-attacks.org + </A><BR> + <I>Fri Jan 21 02:14:40 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002285.html">[Mageia-dev] On the road to build urpmi +</A></li> + <LI>Next message: <A HREF="002286.html">[Mageia-dev] Java-Policy first draft published +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2280">[ date ]</a> + <a href="thread.html#2280">[ thread ]</a> + <a href="subject.html#2280">[ subject ]</a> + <a href="author.html#2280">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Wed, 12 Jan 2011, Frank Griffin wrote: + +><i> Farfouille wrote: +</I>><i> > Hi +</I>><i> > +</I>><i> > I have published a first draft of Java application package policy. <A HREF="http://mageia.org/wiki/doku.php?id=java_applications_policy">http://mageia.org/wiki/doku.php?id=java_applications_policy</A> +</I>><i> > +</I>><i> > Corrections and comments are welcome. +</I>><i> > +</I>><i> +</I>><i> The bit about pre-packaged JARs may cause trouble. In theory, it's +</I>><i> great, but many applications depend upon certain versions of their +</I>><i> utility JARs, and can't all run with the latest versions. Any such app +</I> +Then those applications should be fixed. That's the same with C libraries +or other languages. When a program is not working with a newer version +of its libraries, it is fixed, instead of keeping both the new and old +libraries installed. + +Unless we want to keep 10 versions of each library, each with their owns +bugs and security issues. + +Only when it is really necessary, multiple versions should be kept. + +><i> +</I>><i> Maven POMs allow the packager to specify required other objects +</I>><i> ("artifacts") not only for building the package but for execution as +</I>><i> well. There are central Maven repositories which contain versioned +</I>><i> artifacts for commonly-used projects, e.g. JUnit, and many companies +</I>><i> have site-wide repositories of their own. Finally, every user of Maven +</I>><i> has a personal repository located in $HOME/.m2, which is why the policy +</I>><i> has code for creating this directory. +</I>><i> +</I>><i> Repositories are seached for needed artifacts from the most local (the +</I>><i> user's personal repository) to the most remote (the central Maven +</I>><i> repositories) as directed by a settings.xml file in the user's .m2 +</I>><i> directory or <repositories> tags in the individual pom.xml files. The +</I>><i> general intent is to obtain artifacts from the "closest" repository. +</I>><i> Company repositories are not just the central location for +</I>><i> company-specific artifacts, but also a local cache for central Maven +</I>><i> repository artifacts. +</I>><i> +</I>><i> >From the policy, it looks like the personal repository for the ID under +</I>><i> which RPM builds the package is wiped clean for every package, and thus +</I>><i> every needed artifact will be downloaded from the remote repositories +</I>><i> for every build. If that's the case, it's an awful waste of bandwidth, +</I>><i> since many of these artifacts are used for every Maven project. +</I> +Nothing should be downloaded from remote maven repositories during RPM +builds. All dependencies should be installed from rpm packages only. + +</PRE> + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002285.html">[Mageia-dev] On the road to build urpmi +</A></li> + <LI>Next message: <A HREF="002286.html">[Mageia-dev] Java-Policy first draft published +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2280">[ date ]</a> + <a href="thread.html#2280">[ thread ]</a> + <a href="subject.html#2280">[ subject ]</a> + <a href="author.html#2280">[ 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> |