D'accord pour compiler 2.0.2
Je joins mon script.....je ne comprends pas comment le moidfier pour
récupérer la 2.0.2
Robert Leleu
Je la 06/06/2015 23:54, Lasconic skribis :
I created the 2.0.2 branch but I changed my plan a bit. I was going to
cherry pick the vast majority of the commits of master so I figured
out it was be better to branch master and remove what we didn't want.
So here is what I did.
1/ I created 2.0.2 branch based on master
2/ I talked with Werner and on IRC, I talked with Marc, Jojo, to find
out the changes we did that would make files created in 2.0.2 not look
right in MuseScore 2.0 and 2.0.1. We found a couple of things
* storage of irregular measure and breakMMRest property in measure is
done differently in master
* Master uses the new met* symbol from the last version of bravura in
tempo texts. 2.0 and 2.0.1 don't have this symbol.
3/ I made changes in the 2.0.2 branch to solve these two problems. If
you can think of anything else, or if you find a file made in
nightlies that don't open correctly in 2.0/2.0.1, please report.
4/ I changed the version to 2.0.2 in the code.
Starting from today, nightlies on Mac and nightlies on Windows are
built from the 2.0.2 branch. It would be great if Linux nightlies
could use this branch too.
Regarding translations, I reactivated the push to Transifex and I
removed the -noobsolete flag when calling lupdate. Transifex should
get the strings added in the 2.0.2 branch and keep deleted strings.
However we might have deleted some strings between 2.0 and 2.0.1...
The process in charge of getting strings from transifex and store them
for the resource manager has also been updated and now store the
strings in two folders, one for 2.0.1 and one for 2.0.2. Since we
could have removed strings for 2.0 I didn't do anything yet, so 2.0
will not receive translations updates for now.
Leon, the 2.0.2 branch is based on master. So the pull parser is on by
default.
The addition of this branch doesn't change the development process.
The master branch is still the reference, we should use it to make PR.
I will monitor the commits and cherry pick them in the 2.0.2 branch
until the release. The goal is still end of june, beginning of July.
lasconic
2015-05-29 7:13 GMT+02:00 Leon Vinken <[email protected]
<mailto:[email protected]>>:
Indeed, my preference would be to switch over to the pull parser
by default
a.s.a.p., to get broader test coverage. I have done all the
testing I could
think of, now I need additional testers to find the corner cases I
forgot.
Regards, Leon.
--
View this message in context:
http://dev-list.musescore.org/Preparing-MuseScore-2-0-2-tp7579373p7579431.html
Sent from the MuseScore Developer mailing list archive at Nabble.com.
------------------------------------------------------------------------------
_______________________________________________
Mscore-developer mailing list
[email protected]
<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/mscore-developer
------------------------------------------------------------------------------
_______________________________________________
Mscore-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
#!/bin/bash
# going to compilation directory
MUSEPATH=~/musescore/MuseScore/
cd $MUSEPATH
REVISION_OLD=`cat ./mscore/revision.h`
git reset --hard HEAD
git pull
echo lancement de «make revision >>log
make revision
echo retour de «make revision >>log
REVISION=`cat ./mscore/revision.h`
echo dernière=$REVISION_OLD nouvelle=$REVISION > ~/musescore/log
if [ "$REVISION_OLD" == "$REVISION" -a "$#" -eq "0" ]; then
# if one wants to be advised of any activation of the script, uncomment the two
following lines
zenity --info \
--text='Pas de nouvelle version de MuseScore. '$REVISION_OLD' =
'$REVISION --display=:0
exit
else
zenity --info \
--text='Nouvelle version de MuseScore !'$REVISION_OLD' => '$REVISION
--display=:0
fi
#following line to force 32 bits compilation on a 64 bits computer. To be
uncommented if the computer is 32 bits
#export CFLAGS="-m32"
#CC='gcc -m32' #essai 20/9/13
echo commande "make" >> ~/musescore/log
make >>~/musescore/log
#importing the session password from auxiliary file
MOTDEPASSE=`cat ../motdepassesession`
echo commande "make install" >> ~/musescore/log
echo $MOTDEPASSE | sudo -S make install >>~/musescore/log
cd $MUSEPATH
#building the name of the file to upload
date=$(stat -c %y ./mscore/revision.h)
jour=${date:0:10}
heure=${date:11:2}
minute=${date:14:2}
fin=$(<./mscore/revision.h)
nom="mscore.64bits-"$jour"-"$heure"-"$minute"-"$fin
#creating the file to upload,
cd ./build.release
cd ./mscore
tar -jcvf ../../../historique/$nom.tar.bz2 mscore ../../../lancemscore
../../../readme
cd ../../../historique/
#importing the upload identifier from auxiliary file
ftp_site=prereleases.musescore.org
username=`cat ../identifiant`
passwd=`cat ../motdepasse`
echo commande "ftp" >> ~/musescore/log
ftp -n -i $ftp_site <<EOF
user $username $passwd
binary
mput $nom.tar.bz2 >>~/musescore/log
quit
EOF
# displaying the internet page to advise that an upload took place
firefox --display=:0 -new-window http://prereleases.musescore.org/linux/nightly/
#fi
exit 0
------------------------------------------------------------------------------
_______________________________________________
Mscore-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
