summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20110129/002372.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/20110129/002372.html')
-rw-r--r--zarb-ml/mageia-dev/20110129/002372.html101
1 files changed, 101 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110129/002372.html b/zarb-ml/mageia-dev/20110129/002372.html
new file mode 100644
index 000000000..070d4bb84
--- /dev/null
+++ b/zarb-ml/mageia-dev/20110129/002372.html
@@ -0,0 +1,101 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] packages branches and revision numbers when submiting packages with mgarepo
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20packages%20branches%20and%20revision%20numbers%20when%20submiting%0A%09packages%09with%20mgarepo&In-Reply-To=%3C20110129011600.GA21938%40mars-attacks.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+
+ <LINK REL="Next" HREF="002373.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] packages branches and revision numbers when submiting packages with mgarepo</H1>
+ <B>nicolas vigier</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20packages%20branches%20and%20revision%20numbers%20when%20submiting%0A%09packages%09with%20mgarepo&In-Reply-To=%3C20110129011600.GA21938%40mars-attacks.org%3E"
+ TITLE="[Mageia-dev] packages branches and revision numbers when submiting packages with mgarepo">boklm at mars-attacks.org
+ </A><BR>
+ <I>Sat Jan 29 02:16:00 CET 2011</I>
+ <P><UL>
+
+ <LI>Next message: <A HREF="002373.html">[Mageia-dev] packages branches and revision numbers when submiting packages with mgarepo
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#2372">[ date ]</a>
+ <a href="thread.html#2372">[ thread ]</a>
+ <a href="subject.html#2372">[ subject ]</a>
+ <a href="author.html#2372">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Hello,
+
+In Mandriva using repsys it was possible to provide a svn revision number
+when submitting a package. It is still possible to do it using mgarepo,
+but with a separate repository for binary files, it is more difficult.
+The current version of mgarepo tries to find the right revision to use
+for the binrepo (revision from the same date as the revision on the
+specs repository), but it is not always working as expected. I started
+to add an option to be able to specify the binrepo revision to use when
+submiting, but after thinking about it, it's probably not a good idea,
+because it becomes too complicate.
+
+With repsys it's also possible when submiting packages to give an URL
+instead of a package name. This allows creating new branches for a
+package. However we also have a problem with this with binrepo, as we
+need to find the right path for the binary repository. We could add an
+option to give the URL for the binaries, but I don't think it's a good
+idea.
+
+So I propose to do this instead :
+
+ - We won't allow using revision numbers when submiting packages.
+ Instead we always use the latest revision available on svn. I don't
+ think submit with a revision number are used much (but maybe I'm wrong ?)
+ and a branch copied from a revision can be used instead, to do the
+ same. And not supporting revision numbers will make mgarepo code more
+ simple.
+
+ - We won't allow submit with a URL, but only with a package name (and
+ the right URL will be generated by the script receiving the submit request
+ on pkgsubmit). To allow using branches, instead we add a --branch option
+ to provide the name of a branch. If no branch name is provided we use
+ the package from this path :
+ /packages/cauldron/[packagename]/current
+ If a branch name is provided we use the package from this path :
+ /packages/cauldron/[packagename]/branches/[branchname]
+ And the same path in the binrepo.
+ Some commands can be added in mgarepo to create, remove, checkout branches.
+
+ With this, the path for branches will be more clear, and the same for
+ all packages (contrary to Mandriva where packages could have some branches
+ in /packages/branches, or in /packages/updates, /packages/updates_release
+ or /packages/cooker or anywhere on the repository).
+
+
+Does anyone see any problem with this ? Or other ideas, or comments ?
+
+</PRE>
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+
+ <LI>Next message: <A HREF="002373.html">[Mageia-dev] packages branches and revision numbers when submiting packages with mgarepo
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#2372">[ date ]</a>
+ <a href="thread.html#2372">[ thread ]</a>
+ <a href="subject.html#2372">[ subject ]</a>
+ <a href="author.html#2372">[ 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>