From the CLI invoke the debugger: lldb ~/Applications/Scribus.app/Contents/MacOS/Scribus.Since you are running Scribus trunk you can help Scribus development by making bug reports informative by generating backtraces of the bugs you encounter. It's not recommended to run 2 different package managers on the same machine. Therefore you will need to choose between one or the other. If you have macports installed most likely you will run in to issues when using Homebrew.Trunk will be subject to be broken by the devs as it goes through the development process.(example: if you made a file using v1.5.0 and then opened it up with a trunk build do not expect it to work correctly again in 1.5.0) Trunk is not backward compatible, in other words, back up any older Scribus formats before you open them using trunk.No bugs for homebrew solutions in the Scribus tracker.If you ignore the above, be prepared to stay on a version that works for you.Don't use 1.5 for production, don't rely on it to work day to day.Important Note (from the Scribus core devs) PreferencesDialog prefsDialog(this, oldPrefs) Struct ApplicationPrefs oldPrefs(prefsManager->appPrefs) Then append the patch to the end of the formula.Ĭlass Scribuspatch ScribusDownloadStrategyĭiff -git a/scribus/scribus.cpp b/scribus/scribus.cpp.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |