Re: maemo-release
On Thu, Nov 12, 2009 at 06:11, Quim Gil quim@nokia.com wrote: [...] If the utilities are really useful [...] That still seems to be an outstanding question in my mind; what does maemo-release do that maemo-version doesn't? If it is something useful, is it going to be changed to return the right version numbers? Cheers, Andrew -- Andrew Flegg -- mailto:and...@bleb.org | http://www.bleb.org/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-release
Hi, Quim Gil wrote: We are asking the renaming of pure end user apps called Maemo Something in order to avoid confusion of what is official and what is not. Just to be clear, when you say what is official, what do you mean? Is this applications shipped with the device by default? Or applications created by Nokia? Or applications in the Nokia applications repository? I'd like to think that eventually, applications written by anyone in the community can become official and be installed by default in future Maemo devices, if they prove themselves capable. Cheers, Dave. (For the rest, I agree - if we're not talking about user-targetted apps, the impact is small - I just want to clarify the meaning of the often-used word official) -- maemo.org docsmaster Email: dne...@maemo.org Jabber: bo...@jabber.org ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-release
Andrew Flegg wrote: That still seems to be an outstanding question in my mind; what does maemo-release do that maemo-version doesn't? If it is something useful, is it going to be changed to return the right version numbers? I also wonder what is the result. Gabriel, can you let us know what are your plans? IMO maemo-version should stay, old SDK versions should stay too to prevent confusion (i.e. gregale being 2.2 etc.) and the http://wiki.maemo.org/Maemo-releases or other documentation should stay too but use maemo-version instead. Someone helped me to discover maemo-version only recently and until now I planned only to read /etc/maemo_version in my debian/rules. The idea about using it in Build-Depends was new to me, thanks for that. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-release
ext Dave Neary wrote: Hi, Quim Gil wrote: We are asking the renaming of pure end user apps called Maemo Something in order to avoid confusion of what is official and what is not. Just to be clear, when you say what is official, what do you mean? A piece of software that Nokia is responsible of, and therefore customers can complain to Nokia about. Is this applications shipped with the device by default? Or applications created by Nokia? Or applications in the Nokia applications repository? I'd like to think that eventually, applications written by anyone in the community can become official and be installed by default in future Maemo devices, if they prove themselves capable. Cheers, Dave. (For the rest, I agree - if we're not talking about user-targetted apps, the impact is small - I just want to clarify the meaning of the often-used word official) -- Quim Gil open source advocate Maemo Devices @ Nokia ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-release
On Nov 10, 2009, at 13:27, Jeremiah Foster wrote: On Nov 10, 2009, at 13:17, Frantisek Dufka wrote: Gabriel Schulhof wrote: maemo-version/maemo-release can solve different Build-Depends: fields maemo version provides also /etc/maemo_version so one can check it in /debian/rules when building the package and act differently (include different files, define different variables) What else is needed? Can we change the name of the package? I know that is PITA, but you risk running afoul of Nokia if your package name begins with maemo, trademark and all that. Can you just swap it around to version-maemo? If you don't change the name, it won't make it through extras-testing: http://wiki.maemo.org/Extras-testing/QA_Checklist#Legal_issues Quote: It needs to be clear that the product is not officially supported by Nokia, Maemo or other commercial entities and trademarks. Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-release
2009/11/10 Jeremiah Foster jerem...@jeremiahfoster.com: On Nov 10, 2009, at 13:27, Jeremiah Foster wrote: On Nov 10, 2009, at 13:17, Frantisek Dufka wrote: Gabriel Schulhof wrote: maemo-version/maemo-release can solve different Build-Depends: fields maemo version provides also /etc/maemo_version so one can check it in /debian/rules when building the package and act differently (include different files, define different variables) What else is needed? Can we change the name of the package? I know that is PITA, but you risk running afoul of Nokia if your package name begins with maemo, trademark and all that. Can you just swap it around to version-maemo? If you don't change the name, it won't make it through extras-testing: http://wiki.maemo.org/Extras-testing/QA_Checklist#Legal_issues Quote: It needs to be clear that the product is not officially supported by Nokia, Maemo or other commercial entities and trademarks. Jeremiah The email address of Gabriel is @nokia.com. Is this an official package ? -- anidel Sent from London, Eng, United Kingdom ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-release
On Nov 11, 2009, at 17:30, Aniello Del Sorbo wrote: If you don't change the name, it won't make it through extras-testing: http://wiki.maemo.org/Extras-testing/QA_Checklist#Legal_issues Quote: It needs to be clear that the product is not officially supported by Nokia, Maemo or other commercial entities and trademarks. Jeremiah The email address of Gabriel is @nokia.com. Is this an official package ? I'm not sure. It's fine with me as far as I'm concerned and if Nokia doesn't mind, then everything is okay! Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-release
ext Jeremiah Foster wrote: Can we change the name of the package? I know that is PITA, but you risk running afoul of Nokia if your package name begins with maemo, trademark and all that. Can you just swap it around to version-maemo? We are asking the renaming of pure end user apps called Maemo Something in order to avoid confusion of what is official and what is not. In this case we are talking about little utilities relevant only to SDK users, am I right? The impactb is minor. If the utilities are really useful then why not even consider them to be officially supported at soe point. Gabriel is a busy guy and I'd prefer not to bother him with this. ;) -- Quim Gil open source advocate Maemo Devices @ Nokia ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-release
Hey! On Mon, 2009-11-09 at 14:59 +0100, ext Frantisek Dufka wrote: I added a package to the extras(-devel)? repositories called maemo-release. It has version 1.0.0 in gregale, 2.0.0 in bora, 3.0.0 in Chinook, etc. ... There already is package named maemo-version in the SDK. And the numbering is different (and consistent with SDK releases), Gregale is 2.2, Bora 3.x, Chinook 4.0, Diablo 4.1, D'oh! I looked for such a package, but I was looking only in extras-devel. I suppose I should've asked around some more. Not good :-( /me is embarrassed Gabriel ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-release
On Nov 10, 2009, at 13:17, Frantisek Dufka wrote: Gabriel Schulhof wrote: I suppose I should've asked around some more. We can still have interesting discussion now :-) Actually I am not sure if maemo-version solves every problem maemo-release wanted to solve or developers need to solve to have same package for more SDK versions. maemo-version/maemo-release can solve different Build-Depends: fields maemo version provides also /etc/maemo_version so one can check it in /debian/rules when building the package and act differently (include different files, define different variables) What else is needed? Can we change the name of the package? I know that is PITA, but you risk running afoul of Nokia if your package name begins with maemo, trademark and all that. Can you just swap it around to version-maemo? Maybe it is just enough to keep in mind that there may be potential naming conflicts in the future and leave the name as it is. Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-release
Gabriel Schulhof wrote: I suppose I should've asked around some more. We can still have interesting discussion now :-) Actually I am not sure if maemo-version solves every problem maemo-release wanted to solve or developers need to solve to have same package for more SDK versions. maemo-version/maemo-release can solve different Build-Depends: fields maemo version provides also /etc/maemo_version so one can check it in /debian/rules when building the package and act differently (include different files, define different variables) What else is needed? How can I differentiate between arm and x86 builds? Example - x86 may use vorbis package but arm can use tremor so Build-Depends: can be different for x86 vs ARM. arm may also benefit from arm specific compiler flags. How can I solve that? Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-release
How can I differentiate between arm and x86 builds? Example - x86 may use vorbis package but arm can use tremor so Build-Depends: can be different for x86 vs ARM. arm may also benefit from arm specific compiler flags. How can I solve that? I'm not sure why would you want to do that in maemo context. You should be able to define architecture specific depencies this way Build-Depends: package-name [armel], package2 [!armel]. Haven't actually tested it, but I think it should work. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-release
Mikko Vartiainen wrote: How can I differentiate between arm and x86 builds? Example - x86 may use vorbis package but arm can use tremor so Build-Depends: can be different for x86 vs ARM. arm may also benefit from arm specific compiler flags. How can I solve that? I'm not sure why would you want to do that in maemo context. Well, yes, my example was vorbis vs tremor but true that tremor/libivorbisdec is in x86 target too so I can use tremor in both. I don't have any other real world example. But still it could be useful to set different compiler flags for arm (vfp, thumb mode) or workaround some stuff not available in stratchbox environment. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-release
On Tue, Nov 10, 2009 at 9:16 AM, Frantisek Dufka duf...@seznam.cz wrote: But still it could be useful to set different compiler flags for arm (vfp, thumb mode) [...] For that I think the standard way is to use dpkg-architecture in debian/rules, e.g.: HOST = $(shell dpkg-architecture -qDEB_HOST_ARCH) ... ifeq ($(HOST),armel) # some ARM specific commands go here endif [...] or workaround some stuff not available in stratchbox environment. I see some packages checking for scratchbox environment by looking for presence of /targets/links/scratchbox.config. This file is only available when you are inside a scratchbox target. Regards, -- Anderson Lizardo OpenBossa Labs - INdT Manaus - Brazil ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
maemo-release
Hey, all! I added a package to the extras(-devel)? repositories called maemo-release. It has version 1.0.0 in gregale, 2.0.0 in bora, 3.0.0 in Chinook, etc. ... The idea behind it is that it should make it easier to prevent having to make multiple sets of binary packages from one source package: one for gregale, one for bora, one for chinook, etc., after making minor changes to the source package. This package seeks to address the following problem: Some packages that are available in, say, Fremantle, are not available in, say Diablo. This causes one to have to have different Depends: and Build-Depends: lines in debian/control so as to suit the different distributions. With the maemo-release package present in the distribution, this problem is avoided, because one can always Depends: package-only-available-in-fremantle | maemo-release ( 5.0.0) I've made a wiki page about this at [0]. HTH, Gabriel [0] http://wiki.maemo.org/Maemo-releases ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-release
On Mon, 2009-11-09 at 12:16 +0200, Gabriel Schulhof wrote: Hey, all! I added a package to the extras(-devel)? repositories called maemo-release. It has version 1.0.0 in gregale, 2.0.0 in bora, 3.0.0 in Chinook, etc. ... Cool... what values did you pick for Mer? David ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-release
Gabriel Schulhof wrote: Hey, all! I added a package to the extras(-devel)? repositories called maemo-release. It has version 1.0.0 in gregale, 2.0.0 in bora, 3.0.0 in Chinook, etc. ... There already is package named maemo-version in the SDK. And the numbering is different (and consistent with SDK releases), Gregale is 2.2, Bora 3.x, Chinook 4.0, Diablo 4.1, Not good :-( Regards, Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
PyMaemo (Python for Maemo) release candidate for Maemo 5 (Fremantle)
Hi, The PyMaemo team is pleased to announce the release candidate of PyMaemo for Maemo 5! This new release is currently available through the extras-devel repository, for installation instructions see: http://pymaemo.garage.maemo.org/installation.html. Note that some PyMaemo packages were automatically promoted to extras-testing/extras because they are dependencies from other promoted applications, so you might be already using the latest versions. We also are proud to present the new look for the PyMaemo website: http://pymaemo.garage.maemo.org/. Comments are welcome :). As part of the new website organization, we moved most of the documentation to the wiki, so the community can easily contribute with fixes/updates to it: http://wiki.maemo.org/PyMaemo What is it? -- Python for Maemo (PyMaemo for short) main objective is to make possible to use Python programming language as the scripting and development language for Maemo Platform, providing a better alternative for fast prototyping and programming in Maemo environment besides the C programming language. Python is for serious programming and to have fun. Python has a nice syntax, it is easy to learn and powerful enough for a vast range of applications, this is why we choose Python for Maemo. What has changed? --- New packages: * python-alarm: 0.1-0maemo1 + complete rewrite of libalarm bindings, now using Cython (note that the API has changed a lot since Diablo, for now check the C API documentation[1] for reference) Updated packages: * python-hildon: 0.9.0-1maemo13 + Lots of bug fixes (including adding a few missing API) * cython: 0.11.2-1maemo1 + Update to latest package in Debian. * gst0.10-python: 0.10.14-2maemo5 + Add python2.5-gstreamer to Provides/Replaces/Conflicts keywords * pyclutter: 0.8.0-1maemo3 + Add opengles-sgx-img-common-dev as an alternative dependency to libgl-dev (libgl-dev was removed from Maemo 5 final ARMEL SDK) * python-osso: 0.4-0maemo1 + Complete rewrite using Cython (earlier version had subtle bugs due to missing sanity checks), plus a few API updates. This new version is API compatible with previous one. * python2.5: 2.5.4-1maemo2 + Drop sbox-ld-preload.dpatch. * pygtk: 2.12.1-6maemo8 + Add mising Maemo specific API and some python2.6 compatibility fixes (note that we do not support python2.6 in Maemo 5, this is a future proof fix). * python-hildondesktop: 0.0.3-1maemo2 + Add support for Status Menu widgets. * ipython: 0.10-1maemo1 + Update to latest release from Debian Bugs fixed: MB#4782, MB#4821, MB#4897, MB#4920, MB#4923, MB#4936, MB#4947, MB#4957, MB#4969, MB#4977, MB#5015, MB#5026, MB#5027, MB#5096, MB#5102, MB#5143, MB#5164, MB#5199, MB#5226, MB#5244 Known issues - python-mafw (Python bindings for MAFW) is still considered alpha quality, and there are a couple of known issues on it: MB#4919: python-mafw: list of missing types to complete methods bindings MB#4824: python-mafw: source_browsing.py example does not work MB#4932: python-mafw: mafw.Source.browse() method is missing MB#4839: python-mafw: mafw.Registry lacks list_plugins() method MB#4849: python-mafw: MafwPluginDescriptorPublic structure is missing Hildon Widgets written in Python may not appear on the Add widget list (see MB#5232). We already have a partial fix for the problem, and will upload a new version for python-hildondesktop soon. As a workaround, you can start the widgets from the command line, as standalone programs. See http://wiki.maemo.org/PyMaemo/HildonDesktop for an example on how to do this. There are some bugs in the current documentation for python-hildon (namely the Python Hildon tutorial and reference manual, see MB#5091 and MB#5141). Due to a mistake while upgrading to the new website layout, this documentation is temporarily unavailable. We are working to fix this and will make them available soon. There are no bindings for GUPnP (MB#4829), libhildonmime (MB#5157), as well for various other Maemo 5 components. We plan to work on providing bindings for these components during the Maemo 5 life cycle. The PyMaemo base set of packages take considerable storage space (MB#5364). We already started experiments with the maemo-optify tool to install biggest things out of root fs, and we plan to reduce a plenty of storage usage by cutting unnecessary things (such as some remaining documentation). Expect next releases to reduce storage usage gradually. We will not migrate to python2.6 in Maemo 5 due to a (unresolved) bug (MB#4734 [18]), where a core SDK package explicitly conflicts with python = 2.6, preventing any further upgrades from the 2.5.x series. This release is supposed to be compatible with previous releases. If you have any issues regarding building or running your Python application on Maemo 5, feel free to contact us (see below for how to contact the PyMaemo team and report bugs). Acknowledgments: - Thanks to everybody who helped making this release
Re: Why can't Nokia/Maemo release consistent versions for an upgrade?
Thanks again for fixing this. I'm did an apt-get update from scratchbox and am getting the new version (through apt-get source, not manually downloading). On Mon, Dec 29, 2008 at 2:28 AM, Soumya Bijjal soumya.3.bij...@nokia.com wrote: Hi, The bluez-utils sources is pointing to version 3.28-0osso6 now. Regards, Soumya Bijjal Soumya.3 (Nokia-D/Helsinki) wrote: Hello! bluez-utils 3.28-0osso7 in the SDK repository is a costly mistake. We sincerely apologize for the pain this has caused. We have tried to rectify it on Friday. But apparently, its source is still not pointing to osso6 version. As soon as this is fixed, I will post here again. Regards, Soumya -Original Message- From: maemo-developers-boun...@maemo.org on behalf of ext tz Sent: Sat 12/20/2008 4:53 PM To: maemo-developers@maemo.org Subject: Re: Why can't Nokia/Maemo release consistent versions for an upgrade? Thank You to Nokia. Bluez-utils 3.28-osso6 appeared on Friday and I'm doing the required fixes to my packaging now. (apt-get update doesn't see it so the Packages.gz generator probably hasn't seen it or something is still cached as apt-get source still pulls osso4). ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Why can't Nokia/Maemo release consistent versions for an upgrade?
Hi, The bluez-utils sources is pointing to version 3.28-0osso6 now. Regards, Soumya Bijjal Soumya.3 (Nokia-D/Helsinki) wrote: Hello! bluez-utils 3.28-0osso7 in the SDK repository is a costly mistake. We sincerely apologize for the pain this has caused. We have tried to rectify it on Friday. But apparently, its source is still not pointing to osso6 version. As soon as this is fixed, I will post here again. Regards, Soumya -Original Message- From: maemo-developers-boun...@maemo.org on behalf of ext tz Sent: Sat 12/20/2008 4:53 PM To: maemo-developers@maemo.org Subject: Re: Why can't Nokia/Maemo release consistent versions for an upgrade? Thank You to Nokia. Bluez-utils 3.28-osso6 appeared on Friday and I'm doing the required fixes to my packaging now. (apt-get update doesn't see it so the Packages.gz generator probably hasn't seen it or something is still cached as apt-get source still pulls osso4). ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Why can't Nokia/Maemo release consistent versions for an upgrade?
Thank you - it seemed to take some time for the package.gz spiders to find things, but everything seems in sync with osso6 and my package is updating properly (from extras-devel - now there is a dichotomy with pre-5.2008 needing osso4 and post needing osso6, but after the upgrade becomes common I can promote it to extras). The biggest annoyance is before the correction there was no history or link or whatever I could use to fix it myself (without causing worse evils than I'm trying to solve). When I tried my own upgrade I had a problem with the SSU and had to reflash my Wimax n810 (the metalayer crawler bug https://bugs.maemo.org/show_bug.cgi?id=3938 which I traced because it happened again with supld and added a long comment explaining where the fix for that needs to be - it affects any /etc/init.d entry). On Sat, Dec 20, 2008 at 12:13 PM, soumya.3.bij...@nokia.com wrote: Hello! bluez-utils 3.28-0osso7 in the SDK repository is a costly mistake. We sincerely apologize for the pain this has caused. We have tried to rectify it on Friday. But apparently, its source is still not pointing to osso6 version. As soon as this is fixed, I will post here again. Regards, Soumya ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Why can't Nokia/Maemo release consistent versions for an upgrade?
Thank You to Nokia. Bluez-utils 3.28-osso6 appeared on Friday and I'm doing the required fixes to my packaging now. (apt-get update doesn't see it so the Packages.gz generator probably hasn't seen it or something is still cached as apt-get source still pulls osso4). ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Why can't Nokia/Maemo release consistent versions for an upgrade?
Hello! bluez-utils 3.28-0osso7 in the SDK repository is a costly mistake. We sincerely apologize for the pain this has caused. We have tried to rectify it on Friday. But apparently, its source is still not pointing to osso6 version. As soon as this is fixed, I will post here again. Regards, Soumya -Original Message- From: maemo-developers-boun...@maemo.org on behalf of ext tz Sent: Sat 12/20/2008 4:53 PM To: maemo-developers@maemo.org Subject: Re: Why can't Nokia/Maemo release consistent versions for an upgrade? Thank You to Nokia. Bluez-utils 3.28-osso6 appeared on Friday and I'm doing the required fixes to my packaging now. (apt-get update doesn't see it so the Packages.gz generator probably hasn't seen it or something is still cached as apt-get source still pulls osso4). ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Why can't Nokia/Maemo release consistent versions for an upgrade?
Over the past few months I've been asking to the point of annoyance what to do about bluez-utils-test since it is Maemo supported, therefore has dependencies on the official version. So with the most recent upgrade my application is now completely uninstallable. On the tablet after the upgrade is: bluez-utils-3.28-0osso6. The only thing in any repository (including source) is labeled osso7! If only for the GPL, where is the exact source corresponding to osso6? I can't (without falsifying versions) build an osso6 version of bluez-utils-test. Upgrading bluez-utils to osso7 breaks osso-software-version-rx44 (which is dependent on osso6). Perhaps this is OK, but I'd rather not force all users to have to uninstall this metapackage (does it happen automatically)? I'm also having problems with the SDK - I can't even do apt-get source to get anything but osso4 there - I have to download the components manually. Worse, no one can install the most recent version of my program since for some reason application manager can't resolve the dependencies. The program is only available as a deb (at http://www.zdez.org), but it sits there and lists python2.5-gnome and python2.5-bluez in the Problems tabs. They aren't user so can't be installed manually/separately, but are in extras. apt-get install will work from the command line, but application manager won't. Is there any way Nokia might release an upgrade of such magnitude to a -devel area first so we can test it and undo any breakage BEFORE the users upgrade and break everything? Is there a reason they aren't providing source to the GPL components of the upgrade? Only older or newer ones (the latter for the sdk)? I am really trying hard to play by the rules, but it seems futile since Nokia comes out of the bluez with upgrades that break everything I'm doing and aren't easily fixed. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Detecting Maemo release version, at runtime and using scripts
Thanks Marius! On 4/7/07, Marius Gedminas [EMAIL PROTECTED] wrote: On Fri, Apr 06, 2007 at 04:46:36PM -0400, Scott Prive wrote: I have a shell-based application which I want to support on Maemo. A small feature of my application is to detect the OS/platform it is running on. To get this information on other Linux, I invoke `lsb_release` (Sadly, this command does not exist in the Internet Tablet OS 2007..). Fallback detection is normally accomplished using `cat /etc/*release` in older Linux/UNIX. For the moment, I have a very frail workaround: grep Nokia /etc/hostname followed by a test on $? Is there a Maemo-specific solution to detecting the platform during script execution? $ cat /etc/osso_software_version RX-34_2007SE_3.2007.10-7_PR_MR0 Marius Gedminas -- We did it for smallpox, we'll also win over on ISO 8859-1 ... ;-) -- Markus Kuhn after eradicating one more ISO 8859-1 file from his disk -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFGF4SakVdEXeem148RAoQkAJ4wEY7N7xgd0li8Ef57lZ5eqHBjtQCdFywi 3kvOgzROwNFMyFMhsaswxEU= =QLhz -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -- -Scott ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Detecting Maemo release version, at runtime and using scripts
On Fri, Apr 06, 2007 at 04:46:36PM -0400, Scott Prive wrote: I have a shell-based application which I want to support on Maemo. A small feature of my application is to detect the OS/platform it is running on. To get this information on other Linux, I invoke `lsb_release` (Sadly, this command does not exist in the Internet Tablet OS 2007..). Fallback detection is normally accomplished using `cat /etc/*release` in older Linux/UNIX. For the moment, I have a very frail workaround: grep Nokia /etc/hostname followed by a test on $? Is there a Maemo-specific solution to detecting the platform during script execution? $ cat /etc/osso_software_version RX-34_2007SE_3.2007.10-7_PR_MR0 Marius Gedminas -- We did it for smallpox, we'll also win over on ISO 8859-1 ... ;-) -- Markus Kuhn after eradicating one more ISO 8859-1 file from his disk signature.asc Description: Digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Detecting Maemo release version, at runtime and using scripts
Hello, I have a shell-based application which I want to support on Maemo. A small feature of my application is to detect the OS/platform it is running on. To get this information on other Linux, I invoke `lsb_release` (Sadly, this command does not exist in the Internet Tablet OS 2007..). Fallback detection is normally accomplished using `cat /etc/*release` in older Linux/UNIX. For the moment, I have a very frail workaround: grep Nokia /etc/hostname followed by a test on $? Is there a Maemo-specific solution to detecting the platform during script execution? Thank you. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
