Developer FAQ - Revision history

polarbear: /* Enabling sudo for user installed scripts */

polarbear — Mon, 04 Jun 2012 05:04:35 GMT

Enabling sudo for user installed scripts

← Older revision		Revision as of 05:04, 4 June 2012
Line 304:		Line 304:

	'''Problem'''		'''Problem'''
-	:Users tend to want to edit /etc/sudoers to allow a command provided by a script they created to run with ~~raise~~ privileges. This is highly likely to result in a bricked device forcing you to re-flash to make it work again from scratch.	+	:Users tend to want to edit /etc/sudoers to allow a command provided by a script they created to run with raised privileges. This is highly likely to result in a bricked device forcing you to re-flash to make it work again from scratch.

	'''Reason'''		'''Reason'''
Line 314:		Line 314:

	'''Action'''		'''Action'''
-	:Add your specific sudo configuration to "<code>/etc/sudoers.d/*</code>" as a new file (courtuesy to the reader, you are ~~advice~~ to read [http://www.sudo.ws/sudo/sudoers.man.html this] to understand how to create sudoers.d/ snippets appropriate for your application or script.	+	:Add your specific sudo configuration to "<code>/etc/sudoers.d/*</code>" as a new file (courtuesy to the reader, you are advised to read [http://www.sudo.ws/sudo/sudoers.man.html this] to understand how to create sudoers.d/ snippets appropriate for your application or script.
	:Run update-sudoers and profit.		:Run update-sudoers and profit.

94.0.224.28: /* Enabling sudo for user installed scripts */

94.0.224.28 — Mon, 02 Apr 2012 11:29:05 GMT

Enabling sudo for user installed scripts

← Older revision		Revision as of 11:29, 2 April 2012
Line 315:		Line 315:
	'''Action'''		'''Action'''
	:Add your specific sudo configuration to "<code>/etc/sudoers.d/*</code>" as a new file (courtuesy to the reader, you are advice to read [http://www.sudo.ws/sudo/sudoers.man.html this] to understand how to create sudoers.d/ snippets appropriate for your application or script.		:Add your specific sudo configuration to "<code>/etc/sudoers.d/*</code>" as a new file (courtuesy to the reader, you are advice to read [http://www.sudo.ws/sudo/sudoers.man.html this] to understand how to create sudoers.d/ snippets appropriate for your application or script.
-	:Run update-~~sudores~~ and profit.	+	:Run update-sudoers and profit.

	== Qt ==		== Qt ==

joerg_rw: Undo revision 45992 by 114.79.28.10 (Talk) vandalism/spam

joerg_rw — Thu, 15 Dec 2011 06:25:46 GMT

Undo revision 45992 by 114.79.28.10 (Talk) vandalism/spam

← Older revision		Revision as of 06:25, 15 December 2011
Line 360:		Line 360:
	{{main\|Documentation/Maemo 5 Developer Guide/Packaging, Deploying and Distributing}}		{{main\|Documentation/Maemo 5 Developer Guide/Packaging, Deploying and Distributing}}

-	As Maemo is based on the Debian operating system, creating packages for Maemo borrows a lot of ~~[http://goo.gl/Dg36c youtube] [http://goo.gl/16GT5 idm]~~ tools and techniques from Debian, however there are [[Packaging#Maemo-specific packaging information\|some Maemo-specific differences]].	+	As Maemo is based on the Debian operating system, creating packages for Maemo borrows a lot of tools and techniques from Debian, however there are [[Packaging#Maemo-specific packaging information\|some Maemo-specific differences]].

	A [[Packaging\|simple guide to get started]] is available.		A [[Packaging\|simple guide to get started]] is available.

114.79.28.10: /* How can I package software for Maemo? */

114.79.28.10 — Thu, 15 Dec 2011 03:06:06 GMT

How can I package software for Maemo?

← Older revision		Revision as of 03:06, 15 December 2011
Line 360:		Line 360:
	{{main\|Documentation/Maemo 5 Developer Guide/Packaging, Deploying and Distributing}}		{{main\|Documentation/Maemo 5 Developer Guide/Packaging, Deploying and Distributing}}

-	As Maemo is based on the Debian operating system, creating packages for Maemo borrows a lot of tools and techniques from Debian, however there are [[Packaging#Maemo-specific packaging information\|some Maemo-specific differences]].	+	As Maemo is based on the Debian operating system, creating packages for Maemo borrows a lot of [http://goo.gl/Dg36c youtube] [http://goo.gl/16GT5 idm] tools and techniques from Debian, however there are [[Packaging#Maemo-specific packaging information\|some Maemo-specific differences]].

	A [[Packaging\|simple guide to get started]] is available.		A [[Packaging\|simple guide to get started]] is available.

joerg_rw: Undo revision 45775 by 70.135.114.247 (Talk) SPAM

joerg_rw — Tue, 22 Nov 2011 02:50:10 GMT

Undo revision 45775 by 70.135.114.247 (Talk) SPAM

← Older revision		Revision as of 02:50, 22 November 2011
Line 394:		Line 394:
	[[Category:Development]]		[[Category:Development]]
	[[Category:Scratchbox]]		[[Category:Scratchbox]]
-	~~[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html cell phone number lookup]~~
	[[Category:Fremantle]]		[[Category:Fremantle]]

70.135.114.247: /* How do I enable extras, extras-testing, and extras-devel in Scratchbox */

70.135.114.247 — Mon, 21 Nov 2011 22:08:00 GMT

How do I enable extras, extras-testing, and extras-devel in Scratchbox

← Older revision		Revision as of 22:08, 21 November 2011
Line 394:		Line 394:
	[[Category:Development]]		[[Category:Development]]
	[[Category:Scratchbox]]		[[Category:Scratchbox]]
		+	[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html cell phone number lookup]
	[[Category:Fremantle]]		[[Category:Fremantle]]

amigadave: /* How do I enable extras, extras-testing, and extras-devel in Scratchbox */ use


amigadave — Mon, 07 Mar 2011 14:28:48 GMT
How do I enable extras, extras-testing, and extras-devel in Scratchbox:  use <code>

		
		
		
		
		
		
		← Older revision
		Revision as of 14:28, 7 March 2011
		
		Line 370:
Line 370:
 === How do I enable extras, extras-testing, and extras-devel in Scratchbox ===  === How do I enable extras, extras-testing, and extras-devel in Scratchbox ===
  
- Add the following lines to /etc/apt/sources.list from within scratchbox: + Add the following lines to <code>/etc/apt/sources.list</code> from within scratchbox:
   deb http://repository.maemo.org/extras/ fremantle free non-free    deb http://repository.maemo.org/extras/ fremantle free non-free
   deb-src http://repository.maemo.org/extras/ fremantle free    deb-src http://repository.maemo.org/extras/ fremantle free



amigadave: /* Build failed: No such file or directory in log file */ use 

amigadave — Mon, 07 Mar 2011 14:28:02 GMT
Build failed: No such file or directory in log file:  use <code>

		
		
		
		
		
		
		← Older revision
		Revision as of 14:28, 7 March 2011
		
		Line 342:
Line 342:
 === Build failed: No such file or directory in log file ===  === Build failed: No such file or directory in log file ===
  
- You probably forgot to specify the correct Build-Depends in debian/control. The autobuilder starts every build with a clean SDK image. If you need any application during building which is not available in the default SDK image, you need to specify it specifically. + You probably forgot to specify the correct Build-Depends in <code>debian/control</code>. The autobuilder starts every build with a clean SDK image. If you need any application during building which is not available in the default SDK image, you need to specify it specifically.
  
 You may verify that your Build-Depends field in debian/control is complete by running  You may verify that your Build-Depends field in debian/control is complete by running
Line 348:
Line 348:
   dpkg-depcheck -m dpkg-buildpackage -rfakeroot -b    dpkg-depcheck -m dpkg-buildpackage -rfakeroot -b
  
- in the source tree.  (You'll need to <code>fakeroot apt-get install devscripts</code> for this to work). + in the source tree.  (You'll need to "<code>fakeroot apt-get install devscripts</code>" for this to work).
  
 === Build failed, works in my own scratchbox ===  === Build failed, works in my own scratchbox ===




amigadave: /* Porting to Fremantle */ add porting link, use 

amigadave — Mon, 07 Mar 2011 14:08:47 GMT
Porting to Fremantle:  add porting link, use <code>

		
		
		
		
		
		
		← Older revision
		Revision as of 14:08, 7 March 2011
		
		Line 218:
Line 218:
  
 == Porting to Fremantle ==  == Porting to Fremantle ==
  + 
  + {{main|Documentation/Maemo 5 Developer Guide/Porting Software}}
  
 This section is intended to consolidate the common errors that occur while trying to port [[Open development/Maemo roadmap/Diablo|Diablo]] applications to [[Open development/Maemo roadmap/Fremantle|Fremantle]]. Feel free to improve this page and/or add additional information.  This section is intended to consolidate the common errors that occur while trying to port [[Open development/Maemo roadmap/Diablo|Diablo]] applications to [[Open development/Maemo roadmap/Fremantle|Fremantle]]. Feel free to improve this page and/or add additional information.
Line 267:
Line 269:
  
 '''Application Manager'''  '''Application Manager'''
- * Icon size: HILDON_ICON_SIZE_FINGER. + * Icon size: <code>HILDON_ICON_SIZE_FINGER</code>
 * In Gimp or Photoshop: 48x48 pixels  * In Gimp or Photoshop: 48x48 pixels
  
 '''Task Launcher'''  '''Task Launcher'''
- * Icon size: HILDON_ICON_SIZE_THUMB. + * Icon size: <code>HILDON_ICON_SIZE_THUMB</code>
 * In Gimp or Photoshop: 64x64 pixels  * In Gimp or Photoshop: 64x64 pixels
  
Line 296:
Line 298:
 '''Action'''  '''Action'''
 :Create '''upstart''' job definitions instead of init scripts.  Information on writing these can be found on http://upstart.ubuntu.com/getting-started.html. However, be aware that the directory used on Maemo 5 is <code>/etc/event.d</code>.  :Create '''upstart''' job definitions instead of init scripts.  Information on writing these can be found on http://upstart.ubuntu.com/getting-started.html. However, be aware that the directory used on Maemo 5 is <code>/etc/event.d</code>.
- :The job script should be placed in /etc/event.d/''package''.  And the package postinst, prerm and postrm should use the ''start --quiet'' and ''stop --quiet'' commands to start and stop the service.  Unfortunately there is no debhelper tool to assist with this. + :The job script should be placed in <code>/etc/event.d/''package''</code>.  And the package postinst, prerm and postrm should use the ''start --quiet'' and ''stop --quiet'' commands to start and stop the service.  Unfortunately there is no debhelper tool to assist with this.
  
  
Line 305:
Line 307:
  
 '''Reason'''  '''Reason'''
- :The /etc/sudoers file seems deceivingly straight forward to edit. It's not: + :The <code>/etc/sudoers</code> file seems deceivingly straight forward to edit. It's not:
     <code>      <code>
      17:27 < MohammadAG51> listen to that advice<BR>       17:27 < MohammadAG51> listen to that advice<BR>
Line 312:
Line 314:
  
 '''Action'''  '''Action'''
- :Add your specific sudo configuration to "/etc/sudoers.d/*" as a new file (courtuesy to the reader, you are advice to read [http://www.sudo.ws/sudo/sudoers.man.html this] to understand how to create sudoers.d/ snippets appropriate for your application or script. + :Add your specific sudo configuration to "<code>/etc/sudoers.d/*</code>" as a new file (courtuesy to the reader, you are advice to read [http://www.sudo.ws/sudo/sudoers.man.html this] to understand how to create sudoers.d/ snippets appropriate for your application or script.
 :Run update-sudores and profit.  :Run update-sudores and profit.
  




amigadave: /* Script "af-sb-init.sh start" aborting */ use ordered list for instructions
amigadave — Mon, 07 Mar 2011 13:52:57 GMT
Script "af-sb-init.sh start" aborting:  use ordered list for instructions

		
		
		
		
		
		
		← Older revision
		Revision as of 13:52, 7 March 2011
		
		Line 179:
Line 179:
 To solve this stop the framework, kill all old processes and start it again. This can be done by:  To solve this stop the framework, kill all old processes and start it again. This can be done by:
  
- * stop the framework: + # stop the framework:<pre>af-sb-init.sh stop</pre>
-  ~] > af-sb-init.sh stop + # kill old processes:<pre>sb-conf killall</pre>
-   + # restart:<pre>af-sb-init.sh start</pre>
- * kill old processes: + 
-  ~] > sb-conf killall + 
-   + 
- * restart: + 
-  ~] > af-sb-init.sh start + 
  
 === How to install the SDK+ on a Linux AMD64 platform? ===  === How to install the SDK+ on a Linux AMD64 platform? ===

← Older revision		Revision as of 06:25, 15 December 2011
Line 360:		Line 360:
	{{main\|Documentation/Maemo 5 Developer Guide/Packaging, Deploying and Distributing}}		{{main\|Documentation/Maemo 5 Developer Guide/Packaging, Deploying and Distributing}}

-	As Maemo is based on the Debian operating system, creating packages for Maemo borrows a lot of ~~[http://goo.gl/Dg36c youtube] [http://goo.gl/16GT5 idm]~~ tools and techniques from Debian, however there are [[Packaging#Maemo-specific packaging information\|some Maemo-specific differences]].	+	As Maemo is based on the Debian operating system, creating packages for Maemo borrows a lot of tools and techniques from Debian, however there are [[Packaging#Maemo-specific packaging information\|some Maemo-specific differences]].

	A [[Packaging\|simple guide to get started]] is available.		A [[Packaging\|simple guide to get started]] is available.

← Older revision		Revision as of 03:06, 15 December 2011
Line 360:		Line 360:
	{{main\|Documentation/Maemo 5 Developer Guide/Packaging, Deploying and Distributing}}		{{main\|Documentation/Maemo 5 Developer Guide/Packaging, Deploying and Distributing}}

-	As Maemo is based on the Debian operating system, creating packages for Maemo borrows a lot of tools and techniques from Debian, however there are [[Packaging#Maemo-specific packaging information\|some Maemo-specific differences]].	+	As Maemo is based on the Debian operating system, creating packages for Maemo borrows a lot of [http://goo.gl/Dg36c youtube] [http://goo.gl/16GT5 idm] tools and techniques from Debian, however there are [[Packaging#Maemo-specific packaging information\|some Maemo-specific differences]].

	A [[Packaging\|simple guide to get started]] is available.		A [[Packaging\|simple guide to get started]] is available.

← Older revision		Revision as of 14:28, 7 March 2011
Line 370:		Line 370:
	=== How do I enable extras, extras-testing, and extras-devel in Scratchbox ===		=== How do I enable extras, extras-testing, and extras-devel in Scratchbox ===

-	Add the following lines to /etc/apt/sources.list from within scratchbox:	+	Add the following lines to <code>/etc/apt/sources.list</code> from within scratchbox:
	deb http://repository.maemo.org/extras/ fremantle free non-free		deb http://repository.maemo.org/extras/ fremantle free non-free
	deb-src http://repository.maemo.org/extras/ fremantle free		deb-src http://repository.maemo.org/extras/ fremantle free

← Older revision		Revision as of 14:28, 7 March 2011
Line 342:		Line 342:
	=== Build failed: No such file or directory in log file ===		=== Build failed: No such file or directory in log file ===

-	You probably forgot to specify the correct Build-Depends in debian/control. The autobuilder starts every build with a clean SDK image. If you need any application during building which is not available in the default SDK image, you need to specify it specifically.	+	You probably forgot to specify the correct Build-Depends in <code>debian/control</code>. The autobuilder starts every build with a clean SDK image. If you need any application during building which is not available in the default SDK image, you need to specify it specifically.

	You may verify that your Build-Depends field in debian/control is complete by running		You may verify that your Build-Depends field in debian/control is complete by running
Line 348:		Line 348:
	dpkg-depcheck -m dpkg-buildpackage -rfakeroot -b		dpkg-depcheck -m dpkg-buildpackage -rfakeroot -b

-	in the source tree. (You'll need to <code>fakeroot apt-get install devscripts</code> for this to work).	+	in the source tree. (You'll need to "<code>fakeroot apt-get install devscripts</code>" for this to work).

	=== Build failed, works in my own scratchbox ===		=== Build failed, works in my own scratchbox ===

← Older revision		Revision as of 14:08, 7 March 2011
Line 218:		Line 218:

	== Porting to Fremantle ==		== Porting to Fremantle ==
		+
		+	{{main\|Documentation/Maemo 5 Developer Guide/Porting Software}}

	This section is intended to consolidate the common errors that occur while trying to port [[Open development/Maemo roadmap/Diablo\|Diablo]] applications to [[Open development/Maemo roadmap/Fremantle\|Fremantle]]. Feel free to improve this page and/or add additional information.		This section is intended to consolidate the common errors that occur while trying to port [[Open development/Maemo roadmap/Diablo\|Diablo]] applications to [[Open development/Maemo roadmap/Fremantle\|Fremantle]]. Feel free to improve this page and/or add additional information.
Line 267:		Line 269:

	'''Application Manager'''		'''Application Manager'''
-	* Icon size: HILDON_ICON_SIZE_FINGER.	+	* Icon size: <code>HILDON_ICON_SIZE_FINGER</code>
	* In Gimp or Photoshop: 48x48 pixels		* In Gimp or Photoshop: 48x48 pixels

	'''Task Launcher'''		'''Task Launcher'''
-	* Icon size: HILDON_ICON_SIZE_THUMB.	+	* Icon size: <code>HILDON_ICON_SIZE_THUMB</code>
	* In Gimp or Photoshop: 64x64 pixels		* In Gimp or Photoshop: 64x64 pixels

Line 296:		Line 298:
	'''Action'''		'''Action'''
	:Create '''upstart''' job definitions instead of init scripts. Information on writing these can be found on http://upstart.ubuntu.com/getting-started.html. However, be aware that the directory used on Maemo 5 is <code>/etc/event.d</code>.		:Create '''upstart''' job definitions instead of init scripts. Information on writing these can be found on http://upstart.ubuntu.com/getting-started.html. However, be aware that the directory used on Maemo 5 is <code>/etc/event.d</code>.
-	:The job script should be placed in /etc/event.d/''package''. And the package postinst, prerm and postrm should use the ''start --quiet'' and ''stop --quiet'' commands to start and stop the service. Unfortunately there is no debhelper tool to assist with this.	+	:The job script should be placed in <code>/etc/event.d/''package''</code>. And the package postinst, prerm and postrm should use the ''start --quiet'' and ''stop --quiet'' commands to start and stop the service. Unfortunately there is no debhelper tool to assist with this.


Line 305:		Line 307:

	'''Reason'''		'''Reason'''
-	:The /etc/sudoers file seems deceivingly straight forward to edit. It's not:	+	:The <code>/etc/sudoers</code> file seems deceivingly straight forward to edit. It's not:
	<code>		<code>
	17:27 < MohammadAG51> listen to that advice<BR>		17:27 < MohammadAG51> listen to that advice<BR>
Line 312:		Line 314:

	'''Action'''		'''Action'''
-	:Add your specific sudo configuration to "/etc/sudoers.d/*" as a new file (courtuesy to the reader, you are advice to read [http://www.sudo.ws/sudo/sudoers.man.html this] to understand how to create sudoers.d/ snippets appropriate for your application or script.	+	:Add your specific sudo configuration to "<code>/etc/sudoers.d/*</code>" as a new file (courtuesy to the reader, you are advice to read [http://www.sudo.ws/sudo/sudoers.man.html this] to understand how to create sudoers.d/ snippets appropriate for your application or script.
	:Run update-sudores and profit.		:Run update-sudores and profit.

← Older revision		Revision as of 13:52, 7 March 2011
Line 179:		Line 179:
	To solve this stop the framework, kill all old processes and start it again. This can be done by:		To solve this stop the framework, kill all old processes and start it again. This can be done by:

-	* stop the framework:	+	# stop the framework:<pre>af-sb-init.sh stop</pre>
-	~] > af-sb-init.sh stop	+	# kill old processes:<pre>sb-conf killall</pre>
-		+	# restart:<pre>af-sb-init.sh start</pre>
-	* kill old processes:	+
-	~] > sb-conf killall	+
-		+
-	* restart:	+
-	~] > af-sb-init.sh start	+

	=== How to install the SDK+ on a Linux AMD64 platform? ===		=== How to install the SDK+ on a Linux AMD64 platform? ===