diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20110113/002103.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20110113/002103.html | 122 |
1 files changed, 122 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110113/002103.html b/zarb-ml/mageia-dev/20110113/002103.html new file mode 100644 index 000000000..eafac2eb2 --- /dev/null +++ b/zarb-ml/mageia-dev/20110113/002103.html @@ -0,0 +1,122 @@ +<!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=%3C4D2E4EDA.7020505%40roadrunner.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002101.html"> + <LINK REL="Next" HREF="002106.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Java-Policy first draft published</H1> + <B>Frank Griffin</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Java-Policy%20first%20draft%20published&In-Reply-To=%3C4D2E4EDA.7020505%40roadrunner.com%3E" + TITLE="[Mageia-dev] Java-Policy first draft published">ftg at roadrunner.com + </A><BR> + <I>Thu Jan 13 02:01:14 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002101.html">[Mageia-dev] Java-Policy first draft published +</A></li> + <LI>Next message: <A HREF="002106.html">[Mageia-dev] Java-Policy first draft published +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2103">[ date ]</a> + <a href="thread.html#2103">[ thread ]</a> + <a href="subject.html#2103">[ subject ]</a> + <a href="author.html#2103">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Renaud MICHEL wrote: +><i> On mercredi 12 janvier 2011 at 23:54, Frank Griffin wrote : +</I>><i> +</I>>><i> Users of things like NetBeans and Eclipse are used to the mechanisms +</I>>><i> provided by those tools for managing plugin installation, and are not +</I>>><i> going to take kindly to having to use rpmdrake instead. +</I>>><i> +</I>><i> Well, I use eclipse everyday (arrive at work, start eclipse and close it at +</I>><i> the end of day before leaving) but I don't like its trying to duplicate what +</I>><i> package managers do better. I want to know what' installed on may computer, +</I>><i> how and where. +</I>><i> +</I> +I think you're the exception. + +><i> For years I used to grab the pre-build archives and manage their +</I>><i> dependencies by hand. A few month ago, I decided to repackage those as rpms +</I>><i> with proper dependencies between packages to have urpmi do the work for me. +</I>><i> It was a little complicated to find in the features and packages where their +</I>><i> dependencies were stored, to extract them automatically at package build. +</I>><i> So I was able to split it in many sub-packages to be able to install only +</I>><i> what I need. +</I>><i> The only downside is that it is built from binary archives and not from +</I>><i> source, but for my own use it does work well. +</I>><i> +</I> +I think you're exceptionally industrious. + +><i> Back to your remark, people who don't like to have eclipse installed via rpm +</I>><i> simply won't. They will continue to download the tarball from eclipse.org +</I>><i> and install the plugins they want, either from archives or update sites. +</I>><i> They can also install only the platform from the rpm and, if the - +</I>><i> configuration and -data options are properly added to eclipse startup, they +</I>><i> will be able to install in their home dir the plugins they want using the +</I>><i> update sites. +</I>><i> +</I> +No they won't. They won't know anything about the distinction between +installing via RPM or via tarball. They'll look in rpmdrake for Eclipse +initially, install it from there, and then use the normal Eclipse +mechanism to install plugins. They'll do this because we tell them to +use rpmdrake to look for software, and they'll do the plugins the way +they're used to or the way the Eclipse docs tell them to. + +><i> I won't comment on maven as I don't know how it works (the last time I tried +</I>><i> to build from source a program using maven I did not find what options I was +</I>><i> supposed to give to the mvn command to have it built). +</I>><i> +</I>><i> +</I> +Maven, like Eclipse and NetBeans, has its own infrastructure for +obtaining artifacts (sort of like plugins). The difference is that it +isn't an active thing like Eclipse plugins. Eclipse won't decide you +need something and automatically install it; Maven will. If Maven needs +an artifact and it isn't already in your repository (because you +installed some RPM that put it there), it will fetch it via HTTP +automatically regardless of whether you have an RPM for it or not. + +The result of all this is that you're wasting your time trying to +package plugins and such as RPMs for these products. People aren't +going to use rpmdrake for this because they are used to doing it a +different way, and you'll end up with an unmaintainable mix of stuff +installed via RPM and stuff installed via whatever. +</PRE> + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002101.html">[Mageia-dev] Java-Policy first draft published +</A></li> + <LI>Next message: <A HREF="002106.html">[Mageia-dev] Java-Policy first draft published +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2103">[ date ]</a> + <a href="thread.html#2103">[ thread ]</a> + <a href="subject.html#2103">[ subject ]</a> + <a href="author.html#2103">[ 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> |