Projects/KDE on Solaris/Status - Revision history

Neverendingo: Text replace - "" to ""

2011-06-29T20:57:31Z

Text replace - "</code>" to "</syntaxhighlight>"

Neverendingo: Text replace - "`" to ""`


2011-06-29T20:48:59Z
Text replace - "<code>" to "<syntaxhighlight lang="text">"

				
				
				
				
			
			← Older revision
			Revision as of 20:48, 29 June 2011
			
Line 172:
Line 172:
  *start konsole     *start konsole  
  *start a new tab for convenience     *start a new tab for convenience  
− *<code>cd /tmp</code><code>/usr/ucb/echo -n "#include <math.h>" > t.c</code><code>cc t.c</code>   + *<syntaxhighlight lang="text">cd /tmp</code><syntaxhighlight lang="text">/usr/ucb/echo -n "#include <math.h>" > t.c</code><syntaxhighlight lang="text">cc t.c</code>  
  *notice how the shell prompt does not come back after the warnings printed by the C compiler     *notice how the shell prompt does not come back after the warnings printed by the C compiler  
  *type exit to close the shell / session / tab   *type exit to close the shell / session / tab
    
  You cannot keep typing indefinitely in a session that is not reading output; it seems like eventually the output from the shell hangs as well. Also, you can hang konsole completely by doing this.   You cannot keep typing indefinitely in a session that is not reading output; it seems like eventually the output from the shell hangs as well. Also, you can hang konsole completely by doing this.



SunTzuTech at 16:27, 17 March 2011
2011-03-17T16:27:12Z


				
				
				
				
			
			← Older revision
			Revision as of 16:27, 17 March 2011
			
Line 7:
Line 7:
  == Spec files, and WTF is a DUDE tarball ==   == Spec files, and WTF is a DUDE tarball ==
    
− [http://techbase.kde.org/Projects/KDE_on_Solaris/FOSS_specfiles Spec files] are the mechanism that drives building one of the component software packages.  In there, a discussion is made that examines how the former model of an all-inclusive secret handshake DUDE tarball can be decomposed to the really important pieces which are the patches, configuration, build and install instructions.  For packages without DUDE tarballs, there's enough there to get you started.  We can rely on the internet to download current and possibly obsolete sources to build a package.  What this really means is that while you are starting out, you don't have to download 7GB of stuff just to get started. You get mercurial, a checkout of the specfiles, tweak some stuff on your Solaris system with Studio 12.2 compiler and start building.  Having a decent internet connection is probably a good thing, and if not, figure out a way to get stdcxx, current qt source (4.7.1 now), and a few others to your SOURCES directory.  Overnight downloads or a USB Key/USB Disk at work to transport home always can make a slow internet connection less *painful*. + [http://techbase.kde.org/Projects/KDE_on_Solaris/FOSS_specfiles Spec files] are the mechanism that drives building one of the component software packages.  In there, a discussion is made that examines how the former model of an all-inclusive secret handshake DUDE tarball can be decomposed to the really important pieces which are the patches, configuration, build and install instructions.  For packages without DUDE tarballs, there's enough there to get you started.  We can rely on the internet to download current and possibly obsolete sources to build a package.  What this really means is that while you are starting out, you don't have to download 7GB of stuff just to get started. You get mercurial, a checkout of the spec files, tweak some stuff on your Solaris system with Studio 12.2 compiler and start building.  Having a decent internet connection is probably a good thing, and if not, figure out a way to get stdcxx, current qt source (4.7.1 now), and a few others to your SOURCES directory.  Overnight downloads or a USB Key/USB Disk at work to transport home always can make a slow internet connection less *painful*.
    
  == Dependencies TO-DO List  ==   == Dependencies TO-DO List  ==
Line 25:
Line 25:
  The following list is the growing set of dependencies that is being migrated from the old DUDE tarball structure, to complete spec files. Any upgraded spec files can be easily recompiled to the original by just changing the Version or src_ver variable. This is done to retain compatibility with the original 4.1.4 release that was done.     The following list is the growing set of dependencies that is being migrated from the old DUDE tarball structure, to complete spec files. Any upgraded spec files can be easily recompiled to the original by just changing the Version or src_ver variable. This is done to retain compatibility with the original 4.1.4 release that was done.  
    
− There are several sets of modules which require a circular dependency build to effect all the functionality. gettext requires libiconv, but libiconv requires gettext. So we build gettext, then libiconv, then remove gettext and rebuild it again with libiconv support, then rebuild libiconv support with the real gettext support.  Why do we do this?  Cause a really smart guy figured out the dependencies to make them work the way they were really intended to work.  Just slogging some code together eventually results in someone having to figure out why something breaks.    + There are several sets of modules which require a circular dependency build to effect all the functionality. gettext requires libiconv, but libiconv requires gettext. So we build gettext, then libiconv, then remove gettext and rebuild it again with libiconv support, then rebuild libiconv support with the real gettext support.  Why do we do this?  Cause a really smart and dedicated guy figured out the dependencies to make them work the way they were really intended to work.  Just slogging some code together eventually results in someone having to figure out why something breaks.   
    
  *expat-2.0.1 (upgraded from 2.0.0)     *expat-2.0.1 (upgraded from 2.0.0)  
Line 67:
Line 67:
  **mit-kerberos (temp), cyrus-sasl (temp), openldap (temp), mit-kerberos5 (real), cyrus-sasl (real), openldap (real)     **mit-kerberos (temp), cyrus-sasl (temp), openldap (temp), mit-kerberos5 (real), cyrus-sasl (real), openldap (real)  
  *a52dec-0.7.4     *a52dec-0.7.4  
− *amrnb-26104-610, amrwb-26204-700   + *amrnb-26104-610, amrwb-26204-700
  *audiofile-0.2.6 (added extra patches from the F12 repo)     *audiofile-0.2.6 (added extra patches from the F12 repo)  
  *sdl-1.2.11     *sdl-1.2.11  
Line 108:
Line 108:
  *gtk2-2.18.5 (new, port from sfw, thanks Mark)   *gtk2-2.18.5 (new, port from sfw, thanks Mark)
  *ghostscript-8.64 (new, port from sfw, thanks Mark)     *ghostscript-8.64 (new, port from sfw, thanks Mark)  
− *libspectre-0.2.4 (pnew, ort from sfw, thanks Mark) + *libspectre-0.2.4 (new, port from sfw, thanks Mark)
    
  Upcoming:   Upcoming:



SunTzuTech at 15:56, 4 March 2011
2011-03-04T15:56:39Z


				
				
				
				
			
			← Older revision
			Revision as of 15:56, 4 March 2011
			
Line 4:
Line 4:
    
  While Solaris 10 is getting a bit dated, there is one nice thing about building current software on it. Almost nothing conflicts. If it does, then it's something that's done once, and it doesn't pop up again. Unlike SXCE/Nevada/OSOL, where the list of dependencies is changing bi-weekly. I find that just too annoying for words. Another reason, is that for the most part, stuff from Sun's JDS project or the Spec Files Extra project can be prototyped in very quickly, so the benefit of the initial port work is already done. Solaris 10U8 has 64-bit libraries for libssl and libcrypto, which has been a bit of a blocker, and with the addition of a 64-bit libusb library, there shouldn't be much that can't be built.     While Solaris 10 is getting a bit dated, there is one nice thing about building current software on it. Almost nothing conflicts. If it does, then it's something that's done once, and it doesn't pop up again. Unlike SXCE/Nevada/OSOL, where the list of dependencies is changing bi-weekly. I find that just too annoying for words. Another reason, is that for the most part, stuff from Sun's JDS project or the Spec Files Extra project can be prototyped in very quickly, so the benefit of the initial port work is already done. Solaris 10U8 has 64-bit libraries for libssl and libcrypto, which has been a bit of a blocker, and with the addition of a 64-bit libusb library, there shouldn't be much that can't be built.  
  + 
  + == Spec files, and WTF is a DUDE tarball ==
  + 
  + [http://techbase.kde.org/Projects/KDE_on_Solaris/FOSS_specfiles Spec files] are the mechanism that drives building one of the component software packages.  In there, a discussion is made that examines how the former model of an all-inclusive secret handshake DUDE tarball can be decomposed to the really important pieces which are the patches, configuration, build and install instructions.  For packages without DUDE tarballs, there's enough there to get you started.  We can rely on the internet to download current and possibly obsolete sources to build a package.  What this really means is that while you are starting out, you don't have to download 7GB of stuff just to get started. You get mercurial, a checkout of the specfiles, tweak some stuff on your Solaris system with Studio 12.2 compiler and start building.  Having a decent internet connection is probably a good thing, and if not, figure out a way to get stdcxx, current qt source (4.7.1 now), and a few others to your SOURCES directory.  Overnight downloads or a USB Key/USB Disk at work to transport home always can make a slow internet connection less *painful*.
    
  == Dependencies TO-DO List  ==   == Dependencies TO-DO List  ==
Line 21:
Line 25:
  The following list is the growing set of dependencies that is being migrated from the old DUDE tarball structure, to complete spec files. Any upgraded spec files can be easily recompiled to the original by just changing the Version or src_ver variable. This is done to retain compatibility with the original 4.1.4 release that was done.     The following list is the growing set of dependencies that is being migrated from the old DUDE tarball structure, to complete spec files. Any upgraded spec files can be easily recompiled to the original by just changing the Version or src_ver variable. This is done to retain compatibility with the original 4.1.4 release that was done.  
    
− There are several sets of modules which require a circular dependency build to effect all the functionality. gettext requires libiconv, but libiconv requires gettext. So we build gettext, then libiconv, then remove gettext and rebuild it again with libiconv support, then rebuild libiconv support with the real gettext support.   + There are several sets of modules which require a circular dependency build to effect all the functionality. gettext requires libiconv, but libiconv requires gettext. So we build gettext, then libiconv, then remove gettext and rebuild it again with libiconv support, then rebuild libiconv support with the real gettext support.  Why do we do this?  Cause a really smart guy figured out the dependencies to make them work the way they were really intended to work.  Just slogging some code together eventually results in someone having to figure out why something breaks.  
    
  *expat-2.0.1 (upgraded from 2.0.0)     *expat-2.0.1 (upgraded from 2.0.0)  



SunTzuTech at 16:17, 16 March 2010
2010-03-16T16:17:01Z


				
				
				
				
			
			← Older revision
			Revision as of 16:17, 16 March 2010
			
Line 90:
Line 90:
  *imlib2-1.4.0     *imlib2-1.4.0  
  *cups-1.4.2 (upgrade from 1.1.12)     *cups-1.4.2 (upgrade from 1.1.12)  
− *boost-1.36   + *boost-1.42 (upgrade from boost-1.36, thanks Mark)
− *qt-4.6.1 (automoc issue tracked down to issues with iconv, for now no gnu iconv) + *qt-4.6.2 (automoc issue tracked down to issues with iconv, for now no gnu iconv)
  *libgphoto-2.4.2     *libgphoto-2.4.2  
  *sane-backends-1.0.20     *sane-backends-1.0.20  
  *libexif-0.6.19   *libexif-0.6.19
  + *pycups-1.9.48 (port from sfw, use webstack python2.6)
  + *virtuoso-0.6.1 (thanks Jan)
  + *intltool-0.4.6 (new, ideas from sfw)
  + *pyxml-0.8.4
  + *cairo-1.8.8 (new, port from sfw, thanks Mark)
  + *pango-1.26.1 (new, port from sfw, thanks Mark)
  + *atk-1.28 (new, port from sfw, thanks Mark)
  + *gtk2-2.18.5 (new, port from sfw, thanks Mark)
  + *ghostscript-8.64 (new, port from sfw, thanks Mark) 
  + *libspectre-0.2.4 (pnew, ort from sfw, thanks Mark)
  + 
  + Upcoming:
  + *libglade
  + *pygtk
  + *PyQT
  + *PyKDE
  + *system-config-printer
  + 
  + TODO:
  + Upgrade gstreamer, gst-plugins-{base,good,bad,ffmpeg,etc)
  + Upgrade hal and dbus to current JDS levels
  + 
  + Port (not necessary, but should remove an external dependency): 
  + mysql5.1, ruby18, Apache Portable Runtime and Python2.6 to remove
  + dependency from webstack
  + 
  + <br> 
  + == KDE-4.4.1 Module Changes  ==
  + 
  + *KDEgraphics - add support for S10 ghostscript and libspectre
    
  <br>     <br>  





SunTzuTech: KDEkonversation notes
2010-03-01T18:49:25Z
KDEkonversation notes

				
				
				
				
			
			← Older revision
			Revision as of 18:49, 1 March 2010
			
Line 107:
Line 107:
  *KDEwebdev - Adjust packages for S10 since ruby 1.8 is in /opt/webstack   *KDEwebdev - Adjust packages for S10 since ruby 1.8 is in /opt/webstack
  *KDEwebdev - Added Webstack 1.5's ruby 1.8 to the path   *KDEwebdev - Added Webstack 1.5's ruby 1.8 to the path
  + *KDEkonversation - Make sure to use S10's FOSSgettext tools instead of native.
    
    



SunTzuTech: KDE-4.4.0 changes for Solaris 10
2010-03-01T16:50:44Z
KDE-4.4.0 changes for Solaris 10

				
				
				
				
			
			← Older revision
			Revision as of 16:50, 1 March 2010
			
Line 97:
Line 97:
    
  <br>     <br>  
  + == KDE-4.4.0 Module Changes  ==
  + 
  + *KDEwebdev - Added support for libtidy from Webstack 1.5
  + *KDEbase-workspace - Modified startkde patch to include Webstack paths for S10
  + *KDEmultimedia-kmix - Add 4Front's OpenSound System package as a dependency
  + *KDEbindings - Added Webstack 1.5's ruby 1.8 to the path
  + *KDEsdk - Added Webstack's 1.5 apache22 bin to the path for Apache Portable Runtime support
  + *KDEplasma-addons - Add Webstack's 1.5 python2.6 to the path
  + *KDEwebdev - Adjust packages for S10 since ruby 1.8 is in /opt/webstack
  + *KDEwebdev - Added Webstack 1.5's ruby 1.8 to the path
  + 
    
  == Informational  ==   == Informational  ==



SunTzuTech: minor updates, mysql5.1 and ruby18 from Webstack util added to FOSS
2010-02-15T14:32:06Z
minor updates, mysql5.1 and ruby18 from Webstack util added to FOSS

				
				
				
				
			
			← Older revision
			Revision as of 14:32, 15 February 2010
			
Line 7:
Line 7:
  == Dependencies TO-DO List  ==   == Dependencies TO-DO List  ==
    
− Due to a year of neglect, there are some new dependencies that are going to need to be done for Solaris 10. First, mysql-5.1. This is in the osol repo and should be an easy port. Solaris 10 only has mysql-4.x and only a 32-bit client which makes building qt on 64-bit rather problematic.   + Due to a year of neglect, there are some new dependencies that are going to need to be done for Solaris 10. In the short term, we are going to use
  + mysql-5.1 from webstack, until we decide whether we back port the mysql-5.1.37
  + which is in the opensolaris SFW tree.  We are using this version because
  + the 4.x version in Solaris is old, and only has the 32-bit libraries.
    
− Second is ruby18, again which is in the osol repo, and again should be an easy port.   + Ruby18 is also part of Webstack, so we'll use that until we decide that
  + we'll backport the ruby18 that is also in the opensolaris SFW tree.
    
  <br>     <br>  
Line 37:
Line 41:
  *readline-5.2     *readline-5.2  
  *sqlite-3.6.20 (upgraded from 3.3.8)     *sqlite-3.6.20 (upgraded from 3.3.8)  
− *''glib2-2.12.12'' (upgrade to glib2-2.14.6 caused problems with moc/automoc4, so phonon would not build ''1/15/2010'')   + *glib2-2.22.3 (Thanks MarkW, upgraded from 2.14.6 and 2.12.12)  
  *libdvdcss-1.2.10 (upgraded from 1.2.9)     *libdvdcss-1.2.10 (upgraded from 1.2.9)  
  *libdvdread-4.1.3 (upgrade from 0.9.4)     *libdvdread-4.1.3 (upgrade from 0.9.4)  
Line 87:
Line 91:
  *cups-1.4.2 (upgrade from 1.1.12)     *cups-1.4.2 (upgrade from 1.1.12)  
  *boost-1.36     *boost-1.36  
− *qt-4.6.0 + *qt-4.6.1 (automoc issue tracked down to issues with iconv, for now no gnu iconv)
  *libgphoto-2.4.2     *libgphoto-2.4.2  
  *sane-backends-1.0.20     *sane-backends-1.0.20  



SunTzuTech: note some packages which version were reverted.
2010-01-16T14:51:12Z
note some packages which version were reverted.
Show changes


SunTzuTech: l
2010-01-12T23:48:40Z
l

				
				
				
				
			
			← Older revision
			Revision as of 23:48, 12 January 2010
			
Line 3:
Line 3:
  == Philosophy ==   == Philosophy ==
  While Solaris 10 is getting a bit dated, there is one nice thing about building current software on it.  Almost nothing conflicts.  If it does, then it's something that's done once, and it doesn't pop up again. Unlike SXCE/Nevada/OSOL, where the list of dependencies is changing bi-weekly. I find that just too annoying for words.  Another reason, is that for the most part, stuff from Sun's JDS project or the Spec Files Extra project can be prototyped in very quickly, so the benefit of the initial port work is already done.  Solaris 10U8 has 64-bit libraries for libssl and libcrypto, which has been a bit of a blocker, and with the addition of a 64-bit libusb library, there shouldn't be much that can't be built.   While Solaris 10 is getting a bit dated, there is one nice thing about building current software on it.  Almost nothing conflicts.  If it does, then it's something that's done once, and it doesn't pop up again. Unlike SXCE/Nevada/OSOL, where the list of dependencies is changing bi-weekly. I find that just too annoying for words.  Another reason, is that for the most part, stuff from Sun's JDS project or the Spec Files Extra project can be prototyped in very quickly, so the benefit of the initial port work is already done.  Solaris 10U8 has 64-bit libraries for libssl and libcrypto, which has been a bit of a blocker, and with the addition of a 64-bit libusb library, there shouldn't be much that can't be built.
  + 
  + == Dependencies TO-DO List ==
  + Due to a year of neglect, there are some new dependencies that are going to need to be done for Solaris 10.  First, mysql-5.1.  This is in the osol repo and should be an easy port.  Solaris 10 only has mysql-4.x and only a 32-bit client which makes building qt on 64-bit rather problematic.
  + 
  + Second is ruby18, again which is in the osol repo, and again should be an easy port.  
  + 
    
  == Dependencies ==   == Dependencies ==
Line 76:
Line 82:
  * chlib-0.39   * chlib-0.39
  * imlib2-1.4.0   * imlib2-1.4.0
−   + * cups-1.4.2 (upgrade from 1.1.12)
  + * boost-1.36
  + * qt-4.6.0
  + * libgphoto-2.4.2
  + * sane-backends-1.0.20
  + * libexif-0.6.19

← Older revision		Revision as of 18:49, 1 March 2010
Line 107:		Line 107:
	*KDEwebdev - Adjust packages for S10 since ruby 1.8 is in /opt/webstack		*KDEwebdev - Adjust packages for S10 since ruby 1.8 is in /opt/webstack
	*KDEwebdev - Added Webstack 1.5's ruby 1.8 to the path		*KDEwebdev - Added Webstack 1.5's ruby 1.8 to the path
		+	*KDEkonversation - Make sure to use S10's FOSSgettext tools instead of native.

← Older revision		Revision as of 16:50, 1 March 2010
Line 97:		Line 97:

	<br>		<br>
		+	== KDE-4.4.0 Module Changes ==
		+
		+	*KDEwebdev - Added support for libtidy from Webstack 1.5
		+	*KDEbase-workspace - Modified startkde patch to include Webstack paths for S10
		+	*KDEmultimedia-kmix - Add 4Front's OpenSound System package as a dependency
		+	*KDEbindings - Added Webstack 1.5's ruby 1.8 to the path
		+	*KDEsdk - Added Webstack's 1.5 apache22 bin to the path for Apache Portable Runtime support
		+	*KDEplasma-addons - Add Webstack's 1.5 python2.6 to the path
		+	*KDEwebdev - Adjust packages for S10 since ruby 1.8 is in /opt/webstack
		+	*KDEwebdev - Added Webstack 1.5's ruby 1.8 to the path
		+

	== Informational ==		== Informational ==