From: Alex R. <sh...@gr...> - 2007-10-05 15:27:21
|
On Thu, 2007-10-04 at 23:23 -0700, St=C3=A9phane Charette wrote: > > > We need someone to build release packages for us (that's the tar.gz s= ource package we distribute when we make a release, not the distribution sp= ecific packages). Don used to build releases, but he won't be available to = do that anymore. I'm not entirely sure what skills it requires, but I'm sur= e it includes some knowledge of autoconf, make, translations, and other suc= h tools. If you have these skills (or would like to learn) and are willing = to help us out, please let us know. We won't be able to have a 2.2.9 or a 3= .0.0 release until we have someone who can make a release for us. Don't wor= ry if you aren't sure exactly what to do. I'm sure Don will be willing to a= dvise our lucky volunteer. > > > > All that's needed is this: > > $ ./autogen.sh > > $ make distcheck >=20 > So....? I'm somewhat confused. Does this take a long time to do? Is > it really as simple as running these 2 commands in the source > directory? There must be more to it, otherwise we wouldn't be looking > for a volunteer, right? Well, as Don pointed out, building the tarball is the small part of it. As far as building the tarball goes, the above two commands are more than enough. The 'make dist' will create a tarball in a shorter time. The 'make distcheck' also creates a tarball and then unpacks it into a temp dir, builds and installs, then uninstalls, to check that the tarball is completely self sufficient. It does take longer because of this. Depending on what's missing. something will fail and then you need to figure out what is the problem. E.g. if there's a new file with translatable strings and it is not listed in po/POTFILE.in then the translations will break. If there's a new file that is not listed in its directory's Makefile.am then this file won't be packed into the tarball, and the distcheck portion will fail, and so on. Alex --=20 Alexander Roitman http://gramps-project.org |