diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20110110/002044.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20110110/002044.html | 128 |
1 files changed, 128 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110110/002044.html b/zarb-ml/mageia-dev/20110110/002044.html new file mode 100644 index 000000000..f47e7a5fd --- /dev/null +++ b/zarb-ml/mageia-dev/20110110/002044.html @@ -0,0 +1,128 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] [RFC] Ruby packaging policy + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BRFC%5D%20Ruby%20packaging%20policy&In-Reply-To=%3C1294620570.30856.74.camel%40akroma.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002043.html"> + <LINK REL="Next" HREF="002046.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] [RFC] Ruby packaging policy</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BRFC%5D%20Ruby%20packaging%20policy&In-Reply-To=%3C1294620570.30856.74.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-dev] [RFC] Ruby packaging policy">misc at zarb.org + </A><BR> + <I>Mon Jan 10 01:49:30 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002043.html">[Mageia-dev] Importing RPM Groups +</A></li> + <LI>Next message: <A HREF="002046.html">[Mageia-dev] New bugzilla proposal +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2044">[ date ]</a> + <a href="thread.html#2044">[ thread ]</a> + <a href="subject.html#2044">[ subject ]</a> + <a href="author.html#2044">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le vendredi 07 janvier 2011 à 23:45 +0100, Remy CLOUARD a écrit : +><i> Hello there, +</I>><i> +</I>><i> It’s been quite some time since I started working on ruby modules, and +</I>><i> I’ve been working on the policy too. +</I>><i> +</I>><i> You can find the page here: +</I>><i> <A HREF="http://wiki.mandriva.com/en/Policies/Ruby">http://wiki.mandriva.com/en/Policies/Ruby</A> +</I>><i> +</I>><i> Now, there are some things that still need to be clarified. +</I>><i> +</I>><i> The most controversial part is the naming convention. +</I>><i> +</I>><i> Many ruby modules are packaged via gem, and fedora introduced a strange +</I>><i> naming convention, calling their package rubygem-%{gemname}. This +</I>><i> convention was soon followed by other rpm-based distro such as opensuse +</I>><i> and momonga, and we also have some of them. +</I> +This cause problem since we do have rpm present twice ( without people +noticing, as I dicovered when trying to use gitorious ). More ever, this +is confusing for packagers. There is also potential breakage if someone +start to do tarball, then gems, etc etc. + +I have already expressed my opinion on the subject, and still maintain +it : + +ruby rpm should be ruby-*. + +Several people ( Pascal Terjan +<A HREF="http://lists.mandriva.com/cooker/2010-11/msg00063.php">http://lists.mandriva.com/cooker/2010-11/msg00063.php</A> , Guillaume +Rousse ) also raised concern about this when this discovered after being +pushed 1 year ago without discussion +( <A HREF="http://lists.mandriva.com/cooker/2010-03/msg00401.php">http://lists.mandriva.com/cooker/2010-03/msg00401.php</A> ) . + +Python does also have egg, and they play nice with rpm ( ie, we ship +file that make egg think our python module are installed as egg ). +Cpan also provides archives ( but that unused ) + + +><i> I’m not against changing that convention, but this raises also other +</I>><i> questions. +</I>><i> 1) Do we also need to change the provides/requires ? ie +</I>><i> Requires: ruby(%{gemname}) +</I>><i> instead of +</I>><i> Requires: rubygem(%{gemname}) +</I>><i> +</I>><i> 2) is there a way to make youri watch for rubygem-%{gemname} in case we +</I>><i> opt for that change ? Or better, can youri watch for %{gemname} on +</I>><i> rubygems.org ? +</I> +yes. Just need a patch :) + +><i> About files: +</I>><i> shall we keep the gem in the cache directory ? I’m not sure this is +</I>><i> really useful, up till now I added it, but it makes the package a bit +</I>><i> bigger +</I> +Well, what is the goal of keeping the source in two location ? + +><i> Shall we do a -doc subpackage for big packages ? I think it may be +</I>><i> interesting for package that have a lot of documentation and that are +</I>><i> part of an ecosystem (ie, gems required for other packages like +</I>><i> gitorious) +</I> +That's not specific to ruby. Again, we should follow existing +conventions. + +-- +Michael Scherer + +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002043.html">[Mageia-dev] Importing RPM Groups +</A></li> + <LI>Next message: <A HREF="002046.html">[Mageia-dev] New bugzilla proposal +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2044">[ date ]</a> + <a href="thread.html#2044">[ thread ]</a> + <a href="subject.html#2044">[ subject ]</a> + <a href="author.html#2044">[ 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> |