On Fri, 14 Jun 2013, Satish Balay wrote: > On Thu, 13 Jun 2013, Brad Aagaard wrote: > > > In the past I have used the nightly tarball of petsc for our PyLith > > releases. > > Matt created a knepley/pylith branch that we now use with PyLith. I want to > > create a tarball analogous to the nightly tarball for the knepley/pylith > > branch for our upcoming PyLith release. > > you could do: bin/maint/builddist knepley/pylith
That should be: bin/maint/builddist $PETSC_DIR knepley/pylith nd looks like I need to fixup the script to convert knepley/pylith to knepley-pylith [otherwise the script will attempt to generate ~/petsc-knepley/pylith.tar.gz :( satish > > > > I found the builddist script in $PETSC_DIR/bin/maint but it seems to mess > > with > > my current repo (cleaning, etc) and wants to configure with matlab enabled. > > Should I make a clean clone for building the tarball? > > Yes I spin tarballs form a separate/clean repo. > > Since the script was written to not add in superflus stuff into > release tarballs - it attempts to do a thorough 'clean' of the build > tree. > > > What is the recommended > > procedure for customizing the configure options in builddist (the cleaning > > removes any changes I make) so that I get a tarball but don't need extra > > packages like matlab and c2html? > > Hm - I don't think its possible to switch that off from configure > [without some modifications] > > I can spin a nightly tarball for knepley/pylith and place it at the > petsc ftp site - if that would be useful. > > Satish > >
