Re: Fremantle SDK mount command?
Hi, Can anyone tell me how I can get the mount command from within the Maemo 5 SDK? mount is not part of the current release but it will be most likely in the next one. I will keep you up to date on this. Cheers Daniel ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Fwd: FW: Announcing ConnMan.net
Marcel's original message seems to be pending somewhere so I am forwarding it to here. Jukka -Original Message- From: ext Marcel Holtmann [mailto:holtm...@linux.intel.com] Sent: 23 June, 2009 19:47 To: maemo-developers@maemo.org Cc: Rissanen Jukka (Nokia-D/Helsinki) Subject: Announcing ConnMan.net Intel and Nokia are pleased to jointly launch the ConnMan project, an open source project to accelerate and expand development of Internet connection management for Linux Devices. ConnMan will be utilized as a technology within Moblin and Maemo. Connman.net is now the place to bring developers together who are interested in furthering the development of Internet connection management within Linux. Review the source code for more information. ConnMan is licensed under GPLv2, and provides a daemon for managing Internet connections within Linux devices. ConnMan is a fully modular system that can be extended, through plugins, to support all kinds of wired or wireless technologies. Configuration methods, like DHCP and domain name resolving, are implemented using plug-ins as well. The plug-in approach allows for easy adaption and modification for various use cases. Nokia and Intel will jointly maintain the ConnMan project. We'd like to invite all developers to join the connman.net effort and community. Marcel Holtmann, Intel Open Source Technology Center Jukka Rissanen, Nokia Devices, Maemo Software ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Autobuilder and build-dependencies from extras-devel
I'm writing an application (actually a RAW image files viewer, for those interested :-) ) which depends at build time from an external library. I've already packaged this library and I'm ready to upload it to fremantle extras-devel, but I'm wondering ... when I'll be ready to upload the main app source package, it will depend on the (previously uploaded) library package: will the autobuilder correctly manage those dependencies (ie download and install mylibrary-dev package which in turn depends from mylibrary package, both in extras-devel)? Thanks in advance, Luca Donaggio ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder and build-dependencies from extras-devel
On Jun 24, 2009, at 17:11, Luca Donaggio wrote: I'm writing an application (actually a RAW image files viewer, for those interested :-) ) which depends at build time from an external library. I've already packaged this library and I'm ready to upload it to fremantle extras-devel, but I'm wondering ... when I'll be ready to upload the main app source package, it will depend on the (previously uploaded) library package: will the autobuilder correctly manage those dependencies (ie download and install mylibrary-dev package which in turn depends from mylibrary package, both in extras-devel)? Download and install? No. But if you have previously uploaded those libraries to extras-devel then the autobuilder should find them. More on the autobuilder: http://wiki.maemo.org/Uploading_to_Extras#Autobuilder_special_considerations Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder and build-dependencies from extras-devel
i have been caught in this exact scenario recently. and yes, if the library exists in extras or extras-devel then whilst building your application it will find and use them. there is a gotcha though: if you add NEW calls or references or headers into the library since you last updated, it will FAIL because your app will be trying to load in the older versions. it was something I encountered and pondered whether we could make the autobuilder cheat and look in the queued for updating to extras-devel list so that it found the others. but at the end of the day, I just uploaded and got the library through, waited an hour, then sent the app. gary On Wed, Jun 24, 2009 at 3:24 PM, Jeremiah Foster jerem...@jeremiahfoster.com wrote: On Jun 24, 2009, at 17:11, Luca Donaggio wrote: I'm writing an application (actually a RAW image files viewer, for those interested :-) ) which depends at build time from an external library. I've already packaged this library and I'm ready to upload it to fremantle extras-devel, but I'm wondering ... when I'll be ready to upload the main app source package, it will depend on the (previously uploaded) library package: will the autobuilder correctly manage those dependencies (ie download and install mylibrary-dev package which in turn depends from mylibrary package, both in extras-devel)? Download and install? No. But if you have previously uploaded those libraries to extras-devel then the autobuilder should find them. More on the autobuilder: http://wiki.maemo.org/Uploading_to_Extras#Autobuilder_special_considerations Jeremiah ___ 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: Howto correctly place data on the memory card?
Hi, Am Montag 22 Juni 2009 schrieb Kimmo Hämäläinen: Use MMC_MOUNTPOINT and INTERNAL_MMC_MOUNTPOINT environment variables, available since Nokia 770 Internet Tablet. I'm not sure about Scratchbox, since it does not have memory card emulation. The scratchbox doesn't have this which is perfectly fine as i'll then just fall back to using $HOME. But i still have a major problem with this: It doesn't work in the debian/postinst script when running the application installer. I simply added a call to env to my postinst script to be able to see the environment bein used in the application installers log. See below the log i get on my n810. It seems that the worker thread of the app manager that deals with this has been started before the environment was complete. So there are no MMC related entries at all which makes this useless to install data on the memory card. So please let me re-phrase my question: How does a postinst script know where the memory card is? Till hildon-application-manager 2.1.19.1 /usr/bin/dpkg-deb -f '/media/mmc1/Maemo-deb/osm2go_0.7.6-maemo2_armel.deb' /usr/bin/dpkg --install '/media/mmc1/Maemo-deb/osm2go_0.7.6-maemo2_armel.deb' (Reading database ... 20388 files and directories currently installed.) Preparing to replace osm2go 0.7.6-maemo2 (using .../osm2go_0.7.6-maemo2_armel.deb) ... Unpacking replacement osm2go ... Setting up osm2go (0.7.6-maemo2) ... Cache file created successfully. Environment: SUDO_GID=2 USER=root HOME=/home/user SUDO_UID=2 LOGNAME=root TERM=linux PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin DISPLAY=:0.0 LANG=de_DE LC_MESSAGES=de_DE SUDO_COMMAND=/usr/libexec/apt-worker backend /tmp/apt-worker.to /tmp/apt-worker.from /tmp/apt-worker.status /tmp/apt-worker.cancel B SHELL=/bin/sh SUDO_USER=user PWD=/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
[GSoC 09] - Mnemosyne for Maemo
Hello! I have posted the second report on my Mnemosyne for Maemo GSoC project: https://www.assembla.com/wiki/show/pomni/GSoC2009_Report2 Looking forward to your comments and suggestions! Br, Max Usachev. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
PyQt 4.5.x ?
Just out of curiosity, does anyone have the short term plan of getting PyQt 4.5.x in extras-devel ? I can see that lucianomw uploaded some 4.4 point releases as far as mid-May, but the garage PyQt pages look a bit orphaned... ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder and build-dependencies from extras-devel
gary liquid wrote: if you add NEW calls or references or headers into the library since you last updated, it will FAIL because your app will be trying to load in the older versions. I believe many of us have had the same problems. it was something I encountered and pondered whether we could make the autobuilder cheat and look in the queued for updating to extras-devel list so that it found the others. +1 but at the end of the day, I just uploaded and got the library through, waited an hour, then sent the app. That makes unnecessary delay between the moment your application is ready to be released and the final moment when it can be actually announced to the world. What to do in between? Drink a lot of coffee? In the middle of the night perhaps? 1. Upload your library into the extras assistant 2. Wait unspecified time (usually at least ten minutes) 3. See if the build succeeded. If not, go to 1. 4. Wait unspecified time (one hour perhaps) until the library is actually in the extras-devel. 5. Upload your application into the extras assistant. 6. Wait unspecified time (usually at least ten minutes) 7. See if the build succeeded. If not, go to 5. 8. Wait unspecified time (one hour perhaps) until the application is actually in the extras-devel. 9. Promote the library and the application to the extras. 10. Wait unspecified time (one hour perhaps) until the library and the application is actually in the extras. 11. Announce the new version of your application to users. How many hours is 1 - 10? Is there any possibility to make this time shorter? BR, Henrik -- Henrik Hedberg - http://www.henrikhedberg.net/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder and build-dependencies from extras-devel
2009/6/24 Henrik Hedberg henrik.hedb...@innologies.fi: gary liquid wrote: if you add NEW calls or references or headers into the library since you last updated, it will FAIL because your app will be trying to load in the older versions. I believe many of us have had the same problems. Only those, who uploads libsapps at the same time. it was something I encountered and pondered whether we could make the autobuilder cheat and look in the queued for updating to extras-devel list so that it found the others. +1 It's not that simple as it looks from the first look. For example how autobuilder should distinguish between package, which needs to wait for new library to be built uploaded to extras-devel(app depends on new or changed API, provided by that library) and other application, which doesn't use new API and can be successfully built with older version of library(which is already in extras-devel)? This info can be get from versioning build dependencies, but I doubt that many of Maemo contributers use them properly when changing APIs. I was thinking about adding support for multiple package builds to autobuilder. In this case if packages (library and application in our case) is inculded in one build they will be properly ordered for the build and previous build results will be used. But there is at least one open question here: how dput can support this. I didn't investigate this deeper, but from first look I didn't find proper way to support this in dput. It always operates with one package only. Another idea is that autobuilder will always build packages in dependency order and upload results to extras before starting to build dependent packages. Unfortunately this is not in my near plans. I'm going to add functionality to check package installability to aoutobuilder first. I think it's much more important. but at the end of the day, I just uploaded and got the library through, waited an hour, then sent the app. That makes unnecessary delay between the moment your application is ready to be released and the final moment when it can be actually announced to the world. What to do in between? Drink a lot of coffee? In the middle of the night perhaps? 1. Upload your library into the extras assistant 2. Wait unspecified time (usually at least ten minutes) 3. See if the build succeeded. If not, go to 1. 4. Wait unspecified time (one hour perhaps) until the library is actually in the extras-devel. 5. Upload your application into the extras assistant. 6. Wait unspecified time (usually at least ten minutes) 7. See if the build succeeded. If not, go to 5. 8. Wait unspecified time (one hour perhaps) until the application is actually in the extras-devel. 9. Promote the library and the application to the extras. 10. Wait unspecified time (one hour perhaps) until the library and the application is actually in the extras. 11. Announce the new version of your application to users. How many hours is 1 - 10? Is there any possibility to make this time shorter? Sure! We just need to think about it and we'll found how to do this. I explained my ideas above. You can share yours. If anyone is willing to help in impoving autobuilder - you're always welcome: https://garage.maemo.org/projects/extras-cauldron/ -- BR, Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Fremantle SDK mount command?
Kees, Thank you for your help; I was able to get the mount command in Scratchbox by following your instructions. I then discovered that I don't have permissions to actually mount anything from within Scratchbox. So I've given up for now. I think I'll have to wait until some hardware comes out, or until I'm given some new insights into this mess. On Fri, Jun 19, 2009 at 2:01 PM, Kees Jongenburger kees.jongenbur...@gmail.com wrote: Hi Qole On Fri, Jun 19, 2009 at 9:01 PM, Qole qole.tab...@gmail.com wrote: Any help here would be appreciated it was a little searching but the following worked for me (I start off first outside of sbox on ubuntu in /tmp) cd /tmp apt-get source mount ke...@ijssijs:/tmp$ /scratchbox/login [sbox-FREMANTLE_ARMEL: ~] cp -r /tmp/util-linux-2.14.2 . [sbox-FREMANTLE_ARMEL: ~] (cd util-linux-2.14.2 ; ./configure --with-fsprobe=volume_id --prefix=/usr ; make ; fakeroot make install ) [sbox-FREMANTLE_ARMEL: ~] mount rootfs on / type rootfs (rw) [sbox-FREMANTLE_ARMEL: ~] type mount mount is hashed (/bin/mount) ? ##This I don't really understand why did it install there? [sbox-FREMANTLE_ARMEL: ~] file /bin/mount /bin/mount: setuid ELF 32-bit LSB executable, ARM, version 1 (SYSV), for GNU/Linux 2.6.14, dynamically linked (uses shared libs), not stripped On Wed, Jun 17, 2009 at 2:19 PM, Qole qole.tab...@gmail.com wrote: Hello developers, Can anyone tell me how I can get the mount command from within the Maemo 5 SDK? -- enthusiast, n. One whose mind is wholly possessed and heated by what engages it; one who is influenced by a peculiar fervor of mind; an ardent and imaginative person. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers -- enthusiast, n. One whose mind is wholly possessed and heated by what engages it; one who is influenced by a peculiar fervor of mind; an ardent and imaginative person. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Fremantle SDK mount command?
Hi all; me again. On Wed, Jun 24, 2009 at 2:09 PM, I wrote: I then discovered that I don't have permissions to actually mount anything from within Scratchbox. I also tried to chroot from within Scratchbox: /scratchbox/tools/bin/chroot.bin: cannot change root directory to /debian: Operation not permitted So it just isn't going to happen. :( So I've given up for now. I think I'll have to wait until some hardware comes out, or until I'm given some new insights into this mess. -- enthusiast, n. One whose mind is wholly possessed and heated by what engages it; one who is influenced by a peculiar fervor of mind; an ardent and imaginative person. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
