[scribus] no odt support???

John Culleton john at wexfordpress.com
Thu Jun 26 21:45:34 CEST 2008

On Thursday 26 June 2008 02:56:06 pm Craig Bradney wrote:
> d the problem, and it is an omission with some
> > answers I have received today.  I am trying to do the simple
> > thing and compile in the download directory. A model cmake line
> > in the wiki says:
> > /path/to/cmake .
> > -DCMAKE_INSTALL_PREFIX:PATH=/path/to/install/to/scribuscmake/ but
> > today at least two listmates have suggested:
> > /path/to/cmake
> > -DCMAKE_INSTALL_PREFIX:PATH=/path/to/install/to/scribuscmake/ Can
> > you spot the difference? It is a missing period.
> >
> > I am testing it now with an explicit path.  From the
> > directory /usr/local/scribus- I am running:
> > cmake . -DCMAKE_INSTALL_PREFIX:PATH=/usr/local/scribus-
> > if that works I will try the simpler
> > --------------------------------------------------
> > Well it seems to work now.  No errors on startup! Two things to
> > note: 1 Don't forget the first period in cmake!
> > 2. If you have an existing  scribus in /usr/local/bin you have to
> > rename it (or  overlay it)  and copy the latest scribus from
> > ~your work directory/bin to /usr/local/bin. In my case it is in
> > /usr/local/scribus-
> >
> > These points would be useful to put in the INSTALL file.  I'm
> > still going to try to automate the process with a script. Stay
> > tuned!
> Point 1 is kind of true, especially tru if you are doing an in
> source build. We recommend out of source builds as its cleaner,
> especially for those running svn versions.
> so.. cmake <options> <source path> is what I normally use
> i have something like
> svn
> -source , ie -Scribus
> and -builddir
> the cd builddir
> cmake <options> ../Scribus
> where ../Scribus is instead of your .
> You should not really:
> - install into /usr/local/bin.. not for a clean system.. why not
> just make install into /home/john/installs/scribus13312 for
> example? You can equally install into
> /home/john/installs/scribus13311 and have both installed and
> runnable, along with /home/john/installs/scribus135
> - copy files to install.. run make install and use the prefix you
> have set with configure or cmake.
> No wonder you are having issues if you are installing into
> /usr/local/bin and there are preexisting installs! Time to clean up
> your system a little..
> Craig

No the missing period was the only problem with cmake. Once I fixed 
that the cmake install went fine. I agree that at this point the 
old ./configure way is unworkable for Scribus Too many of 
us have stumbled trying to use it. But that is a bug, not a feature. 
it used to work fine. 

You need to look at this from the user's perspective.  I don't develop 
Scribus, you do. We have different needs.  Confusion between versions 
has never been a problem for me. Confusion about the new install 
method has been.  Frankly the fancy versioning you use fixes a 
problem I don't have. 

I have put the (working) cmake command string in a script so I don't 
have to bother the list next time. 

The wiki tends to bury a leaf in a forest, with all kinds of 
strategies which the end user has no need of. Indeed the whole cmake 
process fixes problems that I don't have. For all my app software I 
put each new version in its own directory. Then I compile it. The 
older executable is renamed. The newer one is copied 
to /usr/local/bin. Right now I have in that /usr/local/bin:
scribus ( 
scribus11 ( 
Both work now. 

The directory "local" means just what it says. Software that comes 
with Linux is in /usr/bin. Software that I install resides 
in /usr/local/bin.  That is where you will find executables for 
Scribus, Gimp, Inkscape, two flavors of COBOL and so on. It is on the  
search path for everyone. Going down a third level to /home/whatever 
is overkill for a single user machine.  Suppose I sign on as root?  
Then the Scribus program becomes invisible. 

Long ago I learned the principle of K.I.S.S. , and the companion 
principle: if it ain't broke don't fix it. 
Scribus 1.3.5 which I compiled some time back is located at 
Since it is unstable and, more seriously, incompatible with earlier 
versions I don't use it just now. But I look forward to the day when 
I can safely convert over.  It's a winner.   

I'll hang on to  1.3.3.x because of old projects that need it. With 
TeX I can use the latest version with files that date back 20 years. 
And that IS a feature and not a bug.  

Thanks for your patience. We just have to agree to disagree on the 
cmake philosophy.  

John Culleton
Resources for every author and publisher:

More information about the scribus mailing list