On Tue, 27 Sep 2005 01:20:57 +0100 Kurt Pfeifle <[EMAIL PROTECTED]> babbled:
> (Attention, cross-posting ahead!) > --------------------------------- > > Hi, enlightenment community! > > You may be interested in our latest creation: a klik-able enlightenment > package. > > What, you don't know about klik yet?? > > OK, OK, not everybody reads the "Dot". So here is the pitch: > > http://dot.kde.org/1126867980/ > > Our new e17 package allows you to deliver in a very efficient way a very > recent e17 snapshot to your friends (hey, they may still be on KDE, or > even worse -- so you surely want to show them E's merits, no?) :-) > > What klik provides, is an extremely easy way to "install" software into > user land for short term testing or permanent use. The klik-ified > packages are in essence AppDir bundles (like on Mac OS or NeXT), but > compressed into one filesystem image that can be mounted to a mountpoint > in userspace and run from there. > > It means: you can run several versions of the same application at the > same time, and your system will be unaffected. If you want to get rid > of a software, delete exactly one file. If you want to test a new > software, copy exactly one .cmg file to your system. The basic principle > is > > 1 application == 1 file > > Our klik server (klik.atekon.de) currently has 4000+ packages to offer. > Most of these are auto generated: the klik client uses a "recipe" that > is sent to him from the klik server. The recipe enumerates the (mostly) > .deb package URLs to use and get the binaries; it then contains the > instructions how to create a .cmg image file from the .deb files. That > means the clients mostly create the .cmg file themselves, which makes > the concept very scaleable. > > To install the klik client, run this command: > > wget klik.atekon.de -O - | sh > > and follow the instructions. What this does execatly do, is outlined > in the above linked article. The result is that from now on you simply > type in a Konqueror or Firefox address bar: > > klik://xvier # we recommend to try this first; it is small enough > # to not waste too much of your time should klik not > # work for your distro yet. > klik://enlightenment > klik://kdeedu > etc. > > and the package gets magically onto your system and starts. > > Limitations: klik has been well tested on Kanotix, Knoppix and Debian. > Recently support for SUSE-10.0 and Ubuntu/Kubuntu have been added. We > know that not all packages work on all platforms equally well. We need > more helping hands. > > You can subscribe to the klik@kde.org and klik-devel@kde.org mailing > lists: > > https://mail.kde.org/mailman/listinfo/klik-devel # Developers > https://mail.kde.org/mailman/listinfo/klik # Users > > or visit us in channel #klik on Freenode.net > > The initial announcement of the klik-ified e17 package is to be > found here: > > http://www.kdedevelopers.org/node/1490 > > And finally, here is a challenge to you: > > # Our klik://enlightenment package doesnt work perfectly. F.e., > # on startup, it resets some of the paths we want it to use. > # That means, not all applications are in the menu, or do > # start properly. > > We are sure one of you wants to fix that, and even take over the > maintainership of the klik://enlightenment package. hmm. e17 itself is entirely re-locatable. i made sure it can be auto-aclaged a while back. it detects its own prefix based on the binary (and path and all sorts of magic) - i too the ideas from autopackage and cleaned them up for e itself and put them right into e. the libs though are not relocatable. imlib2 i think we can actually remove if i do some work in edje - the rest then are entirely able to relocate at runtime as they dont use any built in paths at runtime (eet, evas, ecore (except ecore_config), edje, embryo and e17) can be just put anywhere. edje_cc, embryo_cc are problematic though as they do look for includes. i should do the same autowhatevering of those i did to e17 - but then your klick packages coudl eb entirely locatable to anywhere - as long as u maintain the dir tree from prefix up :) so basically as far as the core wm code and its needs - we re almost there "out of the box" anyway :) > Some more hints about package debugging are in recent stories of > this blog: > > http://www.kdedevelopers.org/blog/418 > > Have fun with enlightenment and klik! > > Cheers, > Simon Peter ("probono" in IRC) > Kurt Pfeifle ("pipitas" in IRC) > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. Download > it for free - -and be entered to win a 42" plasma tv or your very own > Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] 裸好多 Tokyo, Japan (東京 日本) ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
