Thank you Eric, I will look into your suggestions.
Feel free to edit the PKGBUILD locally and let me know about your findings, too!
I will also think about a more suggestive pkgdesc and add a warning to be
printed by the install script.
Am 04. Dezember 2015 05:31:14 MEZ, schrieb ericfontainejazz
<ericfontainej...@gmail.com>:
>I've installed your musescore-git package via yaourt on my arch
>machine. A
>few sugestions:
>
>1) After finish compiling, yaourt checks for conflicting packages and
>says
>"musescore-git and musescore are in conflict. Remove musescore? [y/N]".
> I
>would prefer if these two packages did not conflict, since it is useful
>to
>have both the latest stable and latest git coexisting in the system. I
>think this could be resolved by appending "-git" so the resulting
>binary is
>named "musescore-git".
>
>The instructions here
>https://musescore.org/en/developers-handbook/compilation/compile-instructions-ubuntu-14.10-git#Build-an-executable-file
>lead me to think you can use:
>
>make SUFFIX="-git" LABEL="Git Build"
>sudo make SUFFIX="-git" LABEL="Git Build" install
>
>2) When I go to help->about I see revision is 3543170 but the latest
>commit
>in musescore git master is not that number. I think you need to do
>"make
>revision" first in the arch build script before making musescore so
>that it
>gets that number in that about window. (I'm pretty sure I'm using this
>compiled version by looking at the date on the binary I'm executing)
>
>3) I use distcc and ccache as my default compilers (I've set in my
>/etc/environment). (FYI: distcc allows me to utilize all computers in
>my
>home network when compiling, and ccache supposidly reuses results or
>previous compilations when source files are same to save time).
>Initially
>when trying to build your package via yaourt, I got an error "CMake
>Error...The C++ compiler /usr/bin/ccache is not able to compile a
>simple
>test program"...I've posted full yaourt build output here:
>http://pastebin.com/cz4Y36Kp but suffice to say after switching to
>plain
>CC=gcc and CXX=g++ for compiler variable names, then the build works
>fine.
>Now I haven't looked further into why it failed...it is possible that
>something is wrong with my computer setup, but normally I can build
>musescore just fine via makefile or in qtcreator with distcc and
>ccache. I
>might look into this more...can't say for sure it is the build script's
>fault.
>
>4) I agree that should contain a warning about save file versions. I
>think
>should have a warning in the startup splash screen as well as have the
>build
>script print that warning.
>
>
>
>--
>View this message in context:
>http://dev-list.musescore.org/musescore-git-tp7579555p7579564.html
>Sent from the MuseScore Developer mailing list archive at Nabble.com.
>
>------------------------------------------------------------------------------
>Go from Idea to Many App Stores Faster with Intel(R) XDK
>Give your users amazing mobile app experiences with Intel(R) XDK.
>Use one codebase in this all-in-one HTML5 development environment.
>Design, debug & build mobile apps & 2D/3D high-impact games for
>multiple OSs.
>http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
>_______________________________________________
>Mscore-developer mailing list
>Mscore-developer@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/mscore-developer
------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
_______________________________________________
Mscore-developer mailing list
Mscore-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mscore-developer
