[scribus] 1.5.0svn on holiday

[Dan Horák]

On Wed, 02 Oct 2013 07:50:32 -0400
Gregory Pittman <gpittman at iglou.com> wrote:

> On 10/02/2013 07:29 AM, ZASKE Martin wrote:
> > Dear list,
> > 
> > normally, I am "just" a user and trainer, using Scribus 1.4.3 on
> > Win 7 Pro and Scribus 1.4.2 on OpenSuse 12.3. We are also using
> > Corel X4, because we started with Corel Draw many many years ago.
> > 
> > Now, on holiday, I thought I should have a look at the latest and
> > hottest. This includes the option of buying Corel X6 (on promotion)
> > and looking at Scribus 1.5.0
> > 
> > 
> > I am doing fine with OpenSuse for the last nine years or so and my
> > latest 12.3 is almost up to date. I did try to follow the
> > instructions for getting what is needed and compiling myself.
> > 	One problem is that I am a beginner and have never compiled
> > before. I run into missing-cairo trouble and I believe it is now
> > called cairo2 or something. Also my internet is extremely slow
> > (here in Africa via cell phone), so even getting what I need (once
> > I figure out what I need takes days).
> > 	Also it seems my timing is not ideal with the changes from
> > qt4 to qt5. Seems that even on this list, the experts are still
> > figuring out, what the new instructions should be.
> > 
> > Well, then I figured I could "cheat" a little and I went to
> > 
> > https://build.opensuse.org/package/show?project=KDE%3AUnstable%3APlayground&package=scribus-unstable
> > 
> > I believe this is a place where some people who know make fresh
> > packages. Well I got myself the
> > 
> > scribus-1.5.0svn.18401-148.1.x86_64.rpm
> > 
> > 
> > I discovered that this packet was compiled 8 weeks ago and that it
> > is all based on qt4 rather than qt5, according to
> > 
> > https://build.opensuse.org/package/binary/KDE:Unstable:Playground/scribus-unstable?arch=x86_64&filename=scribus-1.5.0svn.18401-148.1.x86_64.rpm&repository=KDE_Release_410_openSUSE_12.3
> > 
> > 
> > So maybe this means that the experts at KDE playground (no mocking,
> > this is what they call it) are also challenged with the transition
> > to qt5?
> > 
> > On this list it seems to me that several people have already
> > managed to get all needed packages and to compile successfully. So
> > there is hope that our own Scribus wiki will be updated to show
> > what those pioneers have found out. Please write it up, if it works
> > for you; I will then try to do it again. I am looking here:
> > 
> > http://wiki.scribus.net/canvas/Building_SVN_versions_with_CMake
> > 
> > 
> > For today I just have one specific question: I did download 43 MB of
> > this scribus-1.5.0svn.18401-148.1.x86_64.rpm for OpenSuse 12.3
> > 64bit. And even if it is two months old, I still want to install it
> > and see what the new Scribus is all about. But it seems to me that
> > this version 1.5.0 wants to install in the same locations, as my
> > working version 1.4.2.(?) That would be bad; maybe I am wrong. My
> > YAST package manager only will give me all details AFTER
> > installation...
> > 
> > I understand, if I compile myself, I can specify where I want the
> > beast to install. Is there a syntax how I can tell my package
> > manager or zypper that I want this ready made 1.5.0.rpm to install
> > in some trial (sandbox) folder?
> > 
> > 
> > Thank you,
> > 
> > I still got three weeks of holiday, so maybe Scribus will be my
> > first own compile. Or do you think it too big or too ambitious for
> > learning about compiling?
> > 
> 
> My sense of what is happening is that the major distros of Linux are
> all waiting until their next upgrade to finally incorporate qt5
> fully. It's really their fault, since they should have been seeing
> what's going on with various projects incorporating qt5. They seem to
> have this mindset that no one compiles software anymore, so everybody
> will just be happy when qt5-based versions make their way to the
> regular repositories.

there is one problem with Qt5 - it uses v8 as its JavaScript engine and
it means that only x86/x86_64 and ARM architectures are supported.
That's a problem for distros targeting multiple architectures.


		Dan