Talk:Debian 4 Build Instructions - Revision history

Makopoppo: Undo revision 22161 by Makopoppo (Talk)

2011-05-12T14:59:53Z

Undo revision 22161 by Makopoppo (Talk)

Makopoppo: Debian 4 (Etch) has not been supported since over an year ago (Febrary, 2010). For the migration instructions, I'll add the link to debian.org in Build Instructions later

2011-05-12T01:58:15Z

Debian 4 (Etch) has not been supported since over an year ago (Febrary, 2010). For the migration instructions, I'll add the link to debian.org in Build Instructions later

PocoLoco: /* Re: Include a paragraph about placing Mono-2.0.1 in /usr/local/bin */

2009-01-20T16:41:51Z

‎Re: Include a paragraph about placing Mono-2.0.1 in /usr/local/bin

PocoLoco: /* Include a paragraph about placing Mono-2.0.1 in /usr/local/bin */

2009-01-20T16:41:26Z

‎Include a paragraph about placing Mono-2.0.1 in /usr/local/bin

PocoLoco: /* Re: Include a paragraph about placing Mono-2.0.1 in /usr/local/bin */

2009-01-20T16:35:51Z

‎Re: Include a paragraph about placing Mono-2.0.1 in /usr/local/bin

PocoLoco: /* Re: Include a paragraph about placing Mono-2.0.1 in /usr/local/bin */ new section

2009-01-20T16:28:39Z

‎Re: Include a paragraph about placing Mono-2.0.1 in /usr/local/bin: new section

Max Ping at 12:19, 20 January 2009

2009-01-20T12:19:41Z

PocoLoco: /* Include a paragraph about placing Mono-2.0.1 in /usr/local/bin */ new section

2009-01-20T07:52:27Z

‎Include a paragraph about placing Mono-2.0.1 in /usr/local/bin: new section

PocoLoco at 06:35, 20 January 2009

2009-01-20T06:35:42Z

PocoLoco: Sane settings for "--with-libgdiplus"

2009-01-20T06:33:15Z

Sane settings for "--with-libgdiplus"

New page

According to the README in the Source distribution the valid parameters to "--with-libgdiplus=" are

<copy-paste README>
--with-libgdiplus=installed,sibling,<path>
</end copy-paste>

--with-libgdiplus=yes makes no sense

← Older revision		Revision as of 14:59, 12 May 2011
Line 1:		Line 1:
−	~~#Redirect~~ [[Build Instructions#Debian]]	+	According to the README in the Source distribution the valid parameters to "--with-libgdiplus=" are
		+
		+	<copy-paste README>
		+	--with-libgdiplus=installed,sibling,<path>
		+	</end copy-paste>
		+
		+	"--with-libgdiplus=yes" makes no more sense than the instructions previously linked to advising "--with-libgdiplus=no"
		+
		+	== Include a paragraph about placing Mono-2.0.1 in /usr/local/bin ==
		+
		+	I'm thinking it would be a good idea to include instructions for using the command "./configure --prefix=/usr/local" so that this Mono installation gets put in /usr/local/bin so as not to disturb any pre-existing installations of Mono. Most common distros of Linux that have /usr/local/bin in $PATH will have it following /bin and /usr/bin so that software that requires/depends on Mono < 2.0.1 will still find the proper binary when using $PATH. Of course user needs to specify <path> when calling Mono-2.0.1 but seems a small point that is easily remedied. Not to mention the benefit of easily reverting OpenSim to using previous install of Mono by having it still available in /usr/bin
		+	--[[User:PocoLoco\|PocoLoco]] 16:41, 20 January 2009 (UTC)
		+	Naturally i didn't actually read the documentation about the libgdiplus parameters - I was basing that on the opposite of what now appears to be the incorrect original instruction - I propose that we change it to "installed" for the sake of accuracy, although it does seem to work anyway
		+
		+	With reg alternate mono - I suggest that we expand the page to cover all debian distros & mono configs ultimately making it a "deeper" debian experience - I think this page should become "Debian Build Instructions" then an general overview of which configs are supported or work best from our experience
		+
		+	== Re: Include a paragraph about placing Mono-2.0.1 in /usr/local/bin ==
		+
		+	--with-libgdiplus=installed is the default setting. That's why I proposed to drop it completely. Why confuse anyone. If they are interested in the available parameters they will ''read'' the README :-P
		+	As for "other Debian" flavours or versions, I don't think anything previous to Etch has anywhere near the prerequisite packages available and even Etch must use backports to get OpenSim up and running. If Debian versions are going to get split to separate pages we might do a Deb_Etch and Deb_lenny. Apparently there are those that have gotten vanilla Etch serving OpenSim w/just the backports. I don't see any indication from OSgrid forums that the documentation is lacking here for Debian installs. Then again I don't see much indication that anyone reads this wiki b4 enquiry in the forums or irc 8^0
		+	--[[User:PocoLoco\|PocoLoco]] 16:41, 20 January 2009 (UTC)

@@ Line 1: / Line 1: @@
-According to the README in the Source distribution the valid parameters to "--with-libgdiplus=" are
+#Redirect [[Build Instructions#Debian]]
-−
-<copy-paste README>
---with-libgdiplus=installed,sibling,<path>
-</end copy-paste>
-−
-"--with-libgdiplus=yes" makes no more sense than the instructions previously linked to advising "--with-libgdiplus=no"
-−
-== Include a paragraph about placing Mono-2.0.1 in /usr/local/bin ==
-−
-I'm thinking it would be a good idea to include instructions for using the command "./configure --prefix=/usr/local" so that this Mono installation gets put in /usr/local/bin so as not to disturb any pre-existing installations of Mono. Most common distros of Linux that have /usr/local/bin in $PATH will have it following /bin and /usr/bin so that software that requires/depends on Mono < 2.0.1 will still find the proper binary when using $PATH.  Of course user needs to specify <path> when calling Mono-2.0.1 but seems a small point that is easily remedied. Not to mention the benefit of easily reverting OpenSim to using previous install of Mono by having it still available in /usr/bin
- --[[User:PocoLoco|PocoLoco]] 16:41, 20 January 2009 (UTC)
-Naturally i didn't actually read the documentation about the libgdiplus parameters - I was basing that on the opposite of what now appears to be the incorrect original instruction - I propose that we change it to "installed" for the sake of accuracy, although it does seem to work anyway
-−
-With reg alternate mono - I suggest that we expand the page to cover all debian distros & mono configs ultimately making it a "deeper" debian experience - I think this page should become "Debian Build Instructions" then an general overview of which configs are supported or work best from our experience
-−
-== Re: Include a paragraph about placing Mono-2.0.1 in /usr/local/bin  ==
-−
---with-libgdiplus=installed  is the default setting. That's why I proposed to drop it completely. Why confuse anyone. If they are interested in the available parameters they will ''read'' the README :-P
-As for "other Debian" flavours or versions, I don't think anything previous to Etch has anywhere near the prerequisite packages available and even Etch must use backports to get OpenSim up and running. If Debian versions are going to get split to separate pages we might do a Deb_Etch and Deb_lenny. Apparently there are those that have gotten vanilla Etch serving OpenSim w/just the backports. I don't see any indication from OSgrid forums that the documentation is lacking here for Debian installs. Then again I don't see much indication that anyone reads this wiki b4 enquiry in the forums or irc 8^0
---[[User:PocoLoco|PocoLoco]] 16:41, 20 January 2009 (UTC)

← Older revision		Revision as of 16:41, 20 January 2009
Line 19:		Line 19:
	--with-libgdiplus=installed is the default setting. That's why I proposed to drop it completely. Why confuse anyone. If they are interested in the available parameters they will ''read'' the README :-P		--with-libgdiplus=installed is the default setting. That's why I proposed to drop it completely. Why confuse anyone. If they are interested in the available parameters they will ''read'' the README :-P
	As for "other Debian" flavours or versions, I don't think anything previous to Etch has anywhere near the prerequisite packages available and even Etch must use backports to get OpenSim up and running. If Debian versions are going to get split to separate pages we might do a Deb_Etch and Deb_lenny. Apparently there are those that have gotten vanilla Etch serving OpenSim w/just the backports. I don't see any indication from OSgrid forums that the documentation is lacking here for Debian installs. Then again I don't see much indication that anyone reads this wiki b4 enquiry in the forums or irc 8^0		As for "other Debian" flavours or versions, I don't think anything previous to Etch has anywhere near the prerequisite packages available and even Etch must use backports to get OpenSim up and running. If Debian versions are going to get split to separate pages we might do a Deb_Etch and Deb_lenny. Apparently there are those that have gotten vanilla Etch serving OpenSim w/just the backports. I don't see any indication from OSgrid forums that the documentation is lacking here for Debian installs. Then again I don't see much indication that anyone reads this wiki b4 enquiry in the forums or irc 8^0
		+	--[[User:PocoLoco\|PocoLoco]] 16:41, 20 January 2009 (UTC)

@@ Line 10: / Line 10: @@
 I'm thinking it would be a good idea to include instructions for using the command "./configure --prefix=/usr/local" so that this Mono installation gets put in /usr/local/bin so as not to disturb any pre-existing installations of Mono. Most common distros of Linux that have /usr/local/bin in $PATH will have it following /bin and /usr/bin so that software that requires/depends on Mono < 2.0.1 will still find the proper binary when using $PATH.  Of course user needs to specify <path> when calling Mono-2.0.1 but seems a small point that is easily remedied. Not to mention the benefit of easily reverting OpenSim to using previous install of Mono by having it still available in /usr/bin
+ --[[User:PocoLoco|PocoLoco]] 16:41, 20 January 2009 (UTC)
 Naturally i didn't actually read the documentation about the libgdiplus parameters - I was basing that on the opposite of what now appears to be the incorrect original instruction - I propose that we change it to "installed" for the sake of accuracy, although it does seem to work anyway

@@ Line 17: / Line 17: @@
 == Re: Include a paragraph about placing Mono-2.0.1 in /usr/local/bin  ==
---with-libgdiplus=installed  is the default setting. That's why a proposed to drop it completely. Why confuse anyone. If they are interested in the available parameters they will ''read'' the README :-P
+--with-libgdiplus=installed  is the default setting. That's why I proposed to drop it completely. Why confuse anyone. If they are interested in the available parameters they will ''read'' the README :-P
 As for "other Debian" flavours or versions, I don't think anything previous to Etch has anywhere near the prerequisite packages available and even Etch must use backports to get OpenSim up and running. If Debian versions are going to get split to separate pages we might do a Deb_Etch and Deb_lenny. Apparently there are those that have gotten vanilla Etch serving OpenSim w/just the backports. I don't see any indication from OSgrid forums that the documentation is lacking here for Debian installs. Then again I don't see much indication that anyone reads this wiki b4 enquiry in the forums or irc 8^0

← Older revision		Revision as of 16:28, 20 January 2009
Line 14:		Line 14:

	With reg alternate mono - I suggest that we expand the page to cover all debian distros & mono configs ultimately making it a "deeper" debian experience - I think this page should become "Debian Build Instructions" then an general overview of which configs are supported or work best from our experience		With reg alternate mono - I suggest that we expand the page to cover all debian distros & mono configs ultimately making it a "deeper" debian experience - I think this page should become "Debian Build Instructions" then an general overview of which configs are supported or work best from our experience
		+
		+	== Re: Include a paragraph about placing Mono-2.0.1 in /usr/local/bin ==
		+
		+	--with-libgdiplus=installed is the default setting. That's why a proposed to drop it completely. Why confuse anyone. If they are interested in the available parameters they will ''read'' the README :-P
		+	As for "other Debian" flavours or versions, I don't think anything previous to Etch has anywhere near the prerequisite packages available and even Etch must use backports to get OpenSim up and running. If Debian versions are going to get split to separate pages we might do a Deb_Etch and Deb_lenny. Apparently there are those that have gotten vanilla Etch serving OpenSim w/just the backports. I don't see any indication from OSgrid forums that the documentation is lacking here for Debian installs. Then again I don't see much indication that anyone reads this wiki b4 enquiry in the forums or irc 8^0

← Older revision		Revision as of 12:19, 20 January 2009
Line 10:		Line 10:

	I'm thinking it would be a good idea to include instructions for using the command "./configure --prefix=/usr/local" so that this Mono installation gets put in /usr/local/bin so as not to disturb any pre-existing installations of Mono. Most common distros of Linux that have /usr/local/bin in $PATH will have it following /bin and /usr/bin so that software that requires/depends on Mono < 2.0.1 will still find the proper binary when using $PATH. Of course user needs to specify <path> when calling Mono-2.0.1 but seems a small point that is easily remedied. Not to mention the benefit of easily reverting OpenSim to using previous install of Mono by having it still available in /usr/bin		I'm thinking it would be a good idea to include instructions for using the command "./configure --prefix=/usr/local" so that this Mono installation gets put in /usr/local/bin so as not to disturb any pre-existing installations of Mono. Most common distros of Linux that have /usr/local/bin in $PATH will have it following /bin and /usr/bin so that software that requires/depends on Mono < 2.0.1 will still find the proper binary when using $PATH. Of course user needs to specify <path> when calling Mono-2.0.1 but seems a small point that is easily remedied. Not to mention the benefit of easily reverting OpenSim to using previous install of Mono by having it still available in /usr/bin
		+
		+	Naturally i didn't actually read the documentation about the libgdiplus parameters - I was basing that on the opposite of what now appears to be the incorrect original instruction - I propose that we change it to "installed" for the sake of accuracy, although it does seem to work anyway
		+
		+	With reg alternate mono - I suggest that we expand the page to cover all debian distros & mono configs ultimately making it a "deeper" debian experience - I think this page should become "Debian Build Instructions" then an general overview of which configs are supported or work best from our experience

← Older revision		Revision as of 07:52, 20 January 2009
Line 6:		Line 6:

	"--with-libgdiplus=yes" makes no more sense than the instructions previously linked to advising "--with-libgdiplus=no"		"--with-libgdiplus=yes" makes no more sense than the instructions previously linked to advising "--with-libgdiplus=no"
		+
		+	== Include a paragraph about placing Mono-2.0.1 in /usr/local/bin ==
		+
		+	I'm thinking it would be a good idea to include instructions for using the command "./configure --prefix=/usr/local" so that this Mono installation gets put in /usr/local/bin so as not to disturb any pre-existing installations of Mono. Most common distros of Linux that have /usr/local/bin in $PATH will have it following /bin and /usr/bin so that software that requires/depends on Mono < 2.0.1 will still find the proper binary when using $PATH. Of course user needs to specify <path> when calling Mono-2.0.1 but seems a small point that is easily remedied. Not to mention the benefit of easily reverting OpenSim to using previous install of Mono by having it still available in /usr/bin

← Older revision		Revision as of 06:35, 20 January 2009
Line 5:		Line 5:
	</end copy-paste>		</end copy-paste>

−	--with-libgdiplus=yes makes no sense	+	"--with-libgdiplus=yes" makes no more sense than the instructions previously linked to advising "--with-libgdiplus=no"