denemo-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Denemo-devel] The release branch


From: Nils Gey
Subject: Re: [Denemo-devel] The release branch
Date: Tue, 19 Oct 2010 19:19:26 +0200

When I do these steps on my git...
make clean fails because of no target. There is nothing to clean anyway.
./autogen.sh or sh autogen.sh 

address@hidden denemo]$ ./autogen.sh 
libtoolize: putting auxiliary files in `.'.
libtoolize: linking file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: linking file `m4/libtool.m4'
libtoolize: linking file `m4/ltoptions.m4'
libtoolize: linking file `m4/ltsugar.m4'
libtoolize: linking file `m4/ltversion.m4'
libtoolize: linking file `m4/lt~obsolete.m4'
configure.in:17: installing `./compile'
configure.in:13: installing `./config.guess'
configure.in:13: installing `./config.sub'
configure.in:4: installing `./install-sh'
configure.in:4: installing `./missing'
configure.in:13: installing `./mkinstalldirs'
libsmf/Makefile.am: installing `./depcomp'
Makefile.am: installing `./INSTALL'

and then make dist (or any other make) does not work because it does not know 
the target.

Jeremiah, did you forget some steps? Maybe obvious ones?

Nils


On Sat, 16 Oct 2010 22:24:08 +0100
Richard Shann <address@hidden> wrote:

> On Sat, 2010-10-16 at 12:51 -0500, Jeremiah Benham wrote:
> > 
> > On Oct 16, 2010, at 12:34 PM, Nils Gey <address@hidden> wrote:
> > 
> > > The fixes are in stable-0.8.20
> > > Windows-build is ready.
> > >
> > > Jeremiah, could you create the release tarball now, please?
> > 
> > When I get home from work.
> > 
> > > Maybe you could tell me what is needed to do that, too?
> > 
> > To create the tarball:
> > make clean;
> > ./autogen.sh
> > make dist
> > 
> > Then the FTP instructions:
> > 
> > http://www.gnu.org/prep/maintain/html_node/Automated-Upload-Procedure.html
> > 
> > > I notice the tarball has other files and dirs than git.
> 
> But don't do this bit until we have tested it. Release for Wed
> announcement will be good.
> Richard
> 
> 
> 
> 
> > 
> > Which? Maybe they are added by autotools.
> > 
> > Jeremiah
> > 
> > 
> > 
> > >
> > > greetings,
> > >
> > > Nils
> > >
> > >
> > > On Sat, 16 Oct 2010 16:29:49 +0100
> > > Richard Shann <address@hidden> wrote:
> > >
> > >> As we have had a showstopper bug to fix, I have taken the  
> > >> opportunity to
> > >> fix the spurious includes of lyparserfuncs.h so that the Master  
> > >> branch
> > >> should now be good.
> > >> Aligning the stable-0.8.20 with the master branch will mean reverting
> > >> the change to src/Makefile.am and merging the changes.
> > >> Is that ok?
> > >> Richard
> > >>
> > >> On Sat, 2010-10-16 at 08:47 -0500, Jeremiah Benham wrote:
> > >>>
> > >>> On Oct 16, 2010, at 3:02 AM, Richard Shann  
> > >>> <address@hidden>
> > >>> wrote:
> > >>>
> > >>>> Jeremiah, Nils
> > >>>> I see that you had to re-instate lyparserfuncs.h, presumably  
> > >>>> because I
> > >>>> forgot to delete includes of it from the various files when I  
> > >>>> removed
> > >>>> the old parser.
> > >>>
> > >>> Yeah. I added into the tarball. I could not compile the tarball
> > >>> without including it. If it's supposed to left out I will change  
> > >>> that
> > >>> (making sure it compiles) then and remove it from git.
> > >>>
> > >>>
> > >>>> The puzzle then is, how did clean builds work - in
> > >>>> particular windows gub?
> > >>>
> > >>> Pulling from git provides the file. A tarball created with make dist
> > >>> does not because the file was not mentioned in src/Makefile.am.
> > >>>
> > >>> Jeremiah
> > >>>
> > >>>> I would like to avoid re-building the windows
> > >>>> executable, as it will need re-testing. I am not proposing that  
> > >>>> we be
> > >>>> impossibly fussy here - there are no actual changes of source code
> > >>>> here,
> > >>>> just how you build from source. Executables are unaltered.
> > >>>>
> > >>>> So if you can verify that the sources labelled 0.8.20 do build
> > >>>> correctly
> > >>>> on both platforms we are ready to release on Wednesday next, with  
> > >>>> the
> > >>>> already-built-and-tested windows executable. (This executable  
> > >>>> will not
> > >>>> be different if re-built, since the include file must have been
> > >>>> present,
> > >>>> and it would in any case not affect the resultant binary).
> > >>>>
> > >>>> I have some very good progress to check in now if you can move
> > >>>> master on
> > >>>> to 0.8.21, Anacrusis displaying properly, Breve, Longa and whole
> > >>>> measure
> > >>>> rests, even plain chant all doing the right thing in the Denemo
> > >>>> display
> > >>>> *and* the LilyPond!
> > >>>>
> > >>>> Richard
> > >>>>
> > >>>>
> > >>>>
> > >>>> _______________________________________________
> > >>>> Denemo-devel mailing list
> > >>>> address@hidden
> > >>>> http://lists.gnu.org/mailman/listinfo/denemo-devel
> > >>
> > >>
> > >> _______________________________________________
> > >> Denemo-devel mailing list
> > >> address@hidden
> > >> http://lists.gnu.org/mailman/listinfo/denemo-devel
> > >>
> 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]