[scribus] Possible to install 1.3.3.12 after installing 1.3.5svn?
John Culleton
john at wexfordpress.com
Wed May 27 15:32:21 CEST 2009
On Tuesday 26 May 2009 19:17:40 wayne wrote:
> Owen wrote:
> > On Tue, 26 May 2009 07:50:06 -1000 wayne
> >
> > <shakacat at ukulele.com> wrote:
> >> Craig Bradney wrote:
> >>> You might want to adventure into compiling your
> >>> own version. docs.scribus.net has pretty good
> >>> instructions (follow the cmake option for
> >>> 1.3.3.x if you get into that).
> >>
> >> Thanks for the suggestion. I will try to compile
> >> 1.3.3.13. However, a few questions:
> >>
> >> 1. On the Requirements page, only the requirements
> >> for compiling 1.3.5+ are listed. What about
> >> 1.3.3+?
> >
> > I suggest you download the source and inside, you
> > will find a number of files, three of which are
> > called README, BUILDING, INSTALL
> >
> > Those three files are recommended reading.
> >
> > You will find this in the BUILDING file
> >
> > =================================================================
> >== Requirements: Qt >= 3.3 (3.3.8+ recommended) and
> > not Qt4.x Scribus 1.3.3.x will not compile with Qt
> > 4.x
>
> I have Qt4 installed so does that mean 1.3.3.13 will
> not install on my computer?
>
> >> 3. The instructions proceed: "Then run:
> >>
> >> /usr/bin/cmake ../Scribus
> >> -DCMAKE_INSTALL_PREFIX:PATH=/home/username/scribusinstall/"
> >>
> >>
> >> What does the .. in front of ../Scribus mean? Is
> >> something supposed to go there?
> >
> > I recommend that you perhaps get help through a
> > local linux users group if that is possible, as
> > asking such a question suggests you are unfamiliar
> > with the basics of Linux.
>
> Hmmm. Why bother listing instructions at all? If one is
> familiar with Linux, one should be able to find out how
> to compile anything by one's self.
The traditional way to compile Linux apps, still followed by most
projects :
gunzip,
tar xvf,
cd to new directory,
./configure,
make,
make install.
Scribus is somewhat different since it uses a newer approach
substituting ./cmake for ./configure. This approach gives greater
flexibility but also more complication. Inkscape has its own variant
which is completely different. It took me a while to wrap my head
around it. And I have been using Linux since the days when Slackware
came on 3.5 inch floppies.
If I were king every project would go back to the original way. That
way users wouldn't have to reeducate themselves each time they needed
to update a package. But nobody elected me king :<)
--
John Culleton
Able Indexers and Typesetters
Self/small publishers please visit:
http://wexfordpress.com/tex/shortlist.pdf
http://wexfordpress.com/tex/packagers.pdf
More information about the scribus
mailing list