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-dev/2012-February/011909.html | 114 +++++++++++++++++++++++++++ 1 file changed, 114 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-February/011909.html (limited to 'zarb-ml/mageia-dev/2012-February/011909.html') diff --git a/zarb-ml/mageia-dev/2012-February/011909.html b/zarb-ml/mageia-dev/2012-February/011909.html new file mode 100644 index 000000000..5745bb18d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-February/011909.html @@ -0,0 +1,114 @@ + + + + [Mageia-dev] mgasoft + + + + + + + + + +

[Mageia-dev] mgasoft

+ Anssi Hannula + anssi at mageia.org +
+ Mon Feb 13 16:11:51 CET 2012 +

+
+ +
On 06.02.2012 16:57, nicolas vigier wrote:
+> Hello,
+> 
+> While updating youri and iurt packages yesterday I noticed that it's
+> not easy to make new versions of mageia software that we have on svn
+> soft repository, and each of them has different makefile rules to
+> generate tarballs or sometimes update packages. Most versions are not
+> tagged because you have to write a long command line to do it. So in
+> the train from fosdem yesterday I created a small script to tag versions,
+> create tarballs and publish them on mageia mirrors, for the software on
+> svn soft repository.
+> 
+> You can install it with mgasoft package on cauldron.
+> 
+> To tag a new version :
+> $ mgasoft tag [name] [version]
+> 
+> To create a tarball :
+> $ mgasoft tar [name] [version]
+> Or a tarball from trunk, for testing :
+> $ mgasoft tar [name] trunk
+
+As you say, there is some variation in how tarballs are made. How does
+this 'tar' command generate the tarball?
+
+It is common for the "make dist" (or whatever) to package additional
+files not present in SVN to the tarball, such as 'configure' et al or
+'ChangeLog' (generated from SVN), so one can't directly just put the
+trunk directory in the tarball...
+
+> To publish a tarball on mageia mirrors :
+> $ mgasoft publish [name] [version]
+> This will create this file on mirrors :
+> /software/[name]/[name]-[version].tar.xz
+> 
+> Some things that do not work now :
+>  - software in sub-directories on the svn (like build_system/mgarepo or
+>    build_system/iurt). We can change the script to support this, but it
+>    will become more complicated and slower. Or we can move everything in
+>    the root directory and stop using sub-directories like build_system.
+> 
+> Some things I plan to add :
+>  - gpg signature of the files on mirrors
+>  - upload of the files on binrepo, so you don't need to upload them when
+>    updating the package
+>  - option to download tarball from binrepo instead of generating it (to
+>    create package using the same tarball as on mirrors)
+>  - option to quickly see diff between two versions
+> 
+
+
+-- 
+Anssi Hannula
+
+ + + + + + + + +
+

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