[Mageia-dev] mgasoft

Tue Feb 28 12:01:42 CET 2012

On Mon, 13 Feb 2012, Anssi Hannula wrote:
+
+> 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?
+
+Currently, it only generate a tarball from what is on the svn. It
+doesn't run "make dist" or anything else.
+
+> 
+> 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...
+
+I think it could run "make dist" before, but currently the mgasoft
+command is used on the server to generate the tarball and publish it on
+the mirrors, and it would not be safe to run makefile commands directly
+on this server, so I think we need to change how tarballs are published.
+Maybe generating the tarball on client and upload it with binrepo and
+send the sha1sum to the server to publish it on mirrors, or generate it
+on one of the build nodes.
+
+