> Date: Mon, 7 Sep 2015 08:24:15 +0430
> From: msm1365 at gmail.com
> To: scribus at lists.scribus.net
> Subject: [scribus] release unstable 1.5 for fedora22
> 
> I use
>  http://download.opensuse.org/repositories/home:/mrdocs/
> for find scribus repo for fedora, but isn't repo for fedora 22.
If you want to keep current, it might be easier to build from source.
At least on Fedora 20, except for some of the new importers, all of the 
dependencies are available as RPMs from Fedora's repository.
As a start, run yum groupinstall 'development tools'. Then run "sudo yum 
install" for the packages below and follow the instructions at 
http://wiki.scribus.net/canvas/Download and 
http://wiki.scribus.net/canvas/Building_SVN_versions_with_CMake
svn cmake gcc gcc-c++ ccache qtchooser
apr-devel apr-util-devel flex-static libXp libXp-devel libexif-devel 
libtool-ltdl-devel libusb-devel netpbm-progs t1lib openjpeg-devel openjpeg-libs
turbojpeg turbojpeg-devel boost GraphicsMagick fontconfig-devel libX11-devel  
libXext-devel libXaw-devel Xaw3d-devel libXt-devel poppler-devel poppler-qt5 
poppler-qt5-devel poppler-qt poppler-qt-devel poppler-cpp poppler-cpp-devel  
ncurses-devel freeglut freeglut-devel libpaper libpaper-devel libmspub 
libmspub-devel libvisio libvisio-devel lcms2 lcms2-devel OpenSceneGraph 
OpenSceneGraph-devel podofo podofo-devel GraphicsMagick-devel 
libjpeg-turbo-devel libtiff-devel python-devel hunspell hunspell-devel  
libxml++-devel gtkmm24-devel libgnomecanvasmm26-devel cups-devel 
libstdc++-devel gcc-c++ 
freetype-devel cairo-devel libxml2-devel lcms-devel libpng-devel libjpeg-devel 
libwpg-devel boost boost-devel 
openssl-devel git wget 'freeglut*' 'libXmu-*' libXi-devel libXrandr-devel 
'qt5-qt*'
Regards,William Bader, Director of Research and Development at SCS, 
http://www.newspapersystems.com                                       
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.scribus.net/pipermail/scribus/attachments/20150907/8ce4b9c7/attachment.html>

Reply via email to