[prev in list] [next in list] [prev in thread] [next in thread]
List: klik-devel
Subject: Re: [klik-devel] klik-devel Digest, Vol 14, Issue 3
From: "Jason Taylor" <killerkiwi2005 () gmail ! com>
Date: 2007-03-19 5:54:09
Message-ID: 94dd8f6f0703182254o6476a0ebld63c6af975b1b1a () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Just looking at the fuse wiki page, thinking we should be investigate basing
the xml on the ROX standard and just expand it where necessary
http://rox.sourceforge.net/Manual/Manual/Manual.html#AppDir
* There is a lot of multilingual stuff there that is a duplicate of the
freedesktop.org desktop files spec
http://standards.freedesktop.org/menu-spec/latest/
* It doesn't seem to cover the environment setup and package location's that
we require
Killerkiwi
On 3/19/07, Jason Taylor <killerkiwi2005@gmail.com> wrote:
>
> One word comes to mind ... legend !
>
> This removes the need for the runtime script and removes a huge security
> issue with klik.
>
> Feel free to update the klik2 wiki page with these changes.
>
> We'll need to lock down the xml to a nice spec
>
> Killerkiwi
>
>
>
>
>
>
> On 3/18/07, klik-devel-request@kde.org < klik-devel-request@kde.org>
> wrote:
> >
> > Send klik-devel mailing list submissions to
> > klik-devel@kde.org
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> > https://mail.kde.org/mailman/listinfo/klik-devel
> > or, via email, send a message with subject or body 'help' to
> > klik-devel-request@kde.org
> >
> > You can reach the person managing the list at
> > klik-devel-owner@kde.org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of klik-devel digest..."
> >
> >
> > Today's Topics:
> >
> > 1. klikutils + recipe.xml (Lionel Tricon)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Sat, 17 Mar 2007 13:52:37 +0100
> > From: Lionel Tricon < lionel.tricon@free.fr>
> > Subject: [klik-devel] klikutils + recipe.xml
> > To: klik-devel@kde.org
> > Message-ID: < 200703171352.37475.lionel.tricon@free.fr>
> > Content-Type: text/plain; charset="iso-8859-1"
> >
> > The last available version of klikutils use now an xml file to load
> > informations about what have to be run into the cmg file
> > (/etc/recipe.xml
> > file located into the cmg file).
> >
> > It was inspired by examples given on
> > http://klik.atekon.de/wiki/index.php/Klik2 and on which i applied
> > slightly
> > modifications.
> >
> > The main section to run the application is located into the runtime
> > section (i
> > used SAX to parse this specific section ; all things around can be
> > changed) :
> >
> > <runtime>
> > <appname>/usr/bin/ksudoku</appname>
> > <apprun>/usr/bin/ksudoku</apprun>
> > <env>
> > <var name="KDE_FORK_SLAVES" mode="replace">1</var>
> > <var name="PATH" mode="append">/usr/bin</var>
> > <var name="LD_LIBRARY_PATH" mode="append">/usr/lib</var>
> > </env>
> > </runtime>
> >
> > appname: Binary or script to run the application
> > apprun: Binary really started
> >
> > To apply a lot of modifications onto the environment variables before
> > running
> > the application :
> >
> > replace: replace the environment variable
> > For example, <var name="KDE_FORK_SLAVES" mode="replace">1</var> gives
> > "export
> > KDE_FORK_SLAVES=1"
> >
> > append: concat the environment variable to the existing one
> > For example, <var name="PATH" mode="append">/usr/bin</var> fives "export
> > PATH=$PATH:/usr/bin"
> >
> > unset: unset an existing environment variable
> > For example, <var name="FOO" mode="unset"/> gives "unset FOO"
> >
> > For example, for kdissert, it gives us :
> >
> > <?xml version=' 1.0' encoding='UTF-8'?>
> > <recipe creation="2007-03-16 10:43" version="0.1">
> >
> > <name>ksudoku</name>
> > <version>0.3-2</version>
> > <desc>Sudoku puzzle generator/solver</desc>
> > <source>http://klik.atekon.de?application=ksudoku</source>
> > <maintainer>Joe Smith</maintainer>
> >
> > <system required="LSB3">
> > <desktop>/usr/share/applnk/Games/ksudoku.desktop</desktop>
> > <icons>
> > <icon type="png" size="32"
> > src="/usr/share/icons/hicolor/32x32/apps/ksudoku.png"/>
> > </icons>
> > </system>
> >
> > <packages>
> >
> > <package>http://ovh.dl.sourceforge.net/sourceforge/ksudoku/ksudoku_0.3-2_i386.deb
> > </package>
> >
> > <package>
> > ftp://ftp.debian.org/debian/pool/main/n/nas/libaudio2_1.8-3_i386.deb
> > </package>
> > </packages>
> >
> > <runtime>
> > <appname>/usr/bin/ksudoku</appname>
> > <apprun>/usr/bin/ksudoku</apprun>
> > <env>
> > <var name="KDE_FORK_SLAVES" mode="replace">1</var>
> > <var name="PATH" mode="append">/usr/bin</var>
> > <var name="LD_LIBRARY_PATH" mode="append">/usr/lib</var>
> > </env>
> > </runtime>
> >
> > </recipe>
> >
> > I have done a cmg file for bluefish this morning and it works perfectly.
> > I
> > have ran at the same time, bluefish, ksudoku, kdissert and OpenOffice
> > without
> > worry.
> >
> > If you want to test it, remember that you need to call
> > the /opt/klikutils/sh/zAppRun script to launch a cmg file in this
> > version.
> >
> > What do you think ?
> >
> > Lionel
> >
> > On Friday 09 March 2007 16:05:33 Lionel Tricon wrote:
> > > New version of the klikutils bundle which brings some interresting
> > features
> > > : - You can now relocate the /opt/klikutils directory : You need to
> > specify
> > > it into the -u parameter (so you can put the zAppRun script where you
> > want)
> > > - All the wrapper scripts are now located outside the cmg file and
> > then can
> > > be modify more easily (/opt/klikutils/sh directory)
> > >
> > > For the moment, the informations which are used to specify what binary
> > > should be run are available in plain text inside the cmg file.
> > >
> > > # cat /etc/klik.conf
> > > export KLIK_APPNAME="/opt/kde3/bin/kdissert"
> > > export KLIK_APPRUN="/opt/kde3/bin/kdissert"
> > > export KLIK_APPPATH=":/opt/kde3/bin"
> > > export KLIK_APPLIBRARY=":/opt/kde3/lib/kde3"
> > >
> > > The job of the /opt/klikutils/sh/wrapper.env script is to parse this
> > file
> > > to export all these variables.
> > >
> > > If the format of the /etc/klik.conf file change in the futur (for
> > example,
> > > for an xml file), we just have to modify this script to parse in a
> > > different way the klik.conf file (or an another name if you have a
> > better
> > > idea).
> > >
> > > For example, we could reuse the following :
> > >
> > http://linuxfromscratch.org/pipermail/alfs-discuss/2006-January/007537.html
> > >
> > > Important to know that the path of the klikutils bundle is added on
> > the fly
> > > by fuseiso at the end of the wrapper.env script to export the
> > KLIK_BASENAME
> > > variable.
> > >
> > > lionel@linux:~> cat /opt/klikutils/sh/wrapper.env
> > > test -f /etc/klik.conf && . /etc/klik.conf
> > >
> > > lionel@linux:~> cat /tmp/app/1/mnt/wrapper.env
> > > test -f /etc/klik.conf && . /etc/klik.conf
> > > export KLIK_BASENAME=/opt/klikutils
> > >
> > > To test it, please go to http://lionel.tricon.free.fr/KLIK/ as usual.
> > >
> > > I this version, the zAppRun script is available directly into
> > > the /opt/klikutils/sh directory.
> > >
> > > To test the kdissert cmg file in a graphical way under kde, change the
> >
> > > ~/.kde/share/applnk/.hidden/AppRun.desktop file to change the manner
> > how
> > > zAppRun is calling (Exec=/opt/klikutils/sh/zAppRun %U).
> > >
> > > The klikutils bundle contains now the following :
> > > /opt/klikutils/
> > > /opt/klikutils/sh
> > > /opt/klikutils/sh/wrapper.chroot
> > > /opt/klikutils/sh/wrapper.env
> > > /opt/klikutils/sh/zAppRun
> > > /opt/klikutils/sh/wrapper
> > > /opt/klikutils/bin
> > > /opt/klikutils/bin/chroot
> > > /opt/klikutils/bin/fuseiso
> > > /opt/klikutils/bin/fusermount
> > > /opt/klikutils/lib
> > > /opt/klikutils/lib/fakechroot
> > > /opt/klikutils/lib/fakechroot/libfakechroot.so
> > >
> > > If you have any questions or suggestions, don't hesitate to contact
> > me.
> > >
> > > Lionel
> >
> >
> >
> >
> > ------------------------------
> >
> > _______________________________________________
> > klik-devel mailing list
> > klik-devel@kde.org
> > https://mail.kde.org/mailman/listinfo/klik-devel
> >
> >
> > End of klik-devel Digest, Vol 14, Issue 3
> > *****************************************
> >
>
>
[Attachment #5 (text/html)]
Just looking at the fuse wiki page, thinking we should be investigate basing the xml on the ROX \
standard and just expand it where necessary<br><a \
href="http://rox.sourceforge.net/Manual/Manual/Manual.html#AppDir">http://rox.sourceforge.net/Manual/Manual/Manual.html#AppDir
</a><br><br>* There is a lot of multilingual stuff there that is a duplicate of the <a \
href="http://freedesktop.org">freedesktop.org</a> desktop files spec <a \
href="http://standards.freedesktop.org/menu-spec/latest/">http://standards.freedesktop.org/menu-spec/latest/
</a><br>* It doesn't seem to cover the environment setup and package location's that \
we require<br><br><br>Killerkiwi<br><br><div><span class="gmail_quote">On 3/19/07, <b \
class="gmail_sendername">Jason Taylor</b> < <a \
href="mailto:killerkiwi2005@gmail.com">killerkiwi2005@gmail.com</a>> \
wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); \
margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">One word comes to mind ... legend ! <br><br>This \
removes the need for the runtime script and removes a huge security issue with \
klik.<br><br>Feel free to update the klik2 wiki page with these changes.<br><br>We'll need \
to lock down the xml to a nice spec <br><br>Killerkiwi<div><span class="e" \
id="q_11167193c31ddb33_1"><br><br><br><br><br><br><br><div><span class="gmail_quote">On \
3/18/07, <b class="gmail_sendername"><a href="mailto:klik-devel-request@kde.org" \
target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> \
klik-devel-request@kde.org</a></b> <<a href="mailto:klik-devel-request@kde.org" \
target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> \
klik-devel-request@kde.org</a>> wrote:</span><blockquote class="gmail_quote" \
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: \
1ex;">Send klik-devel mailing list submissions to <br>
<a href="mailto:klik-devel@kde.org" \
target="_blank" onclick="return \
top.js.OpenExtLink(window,event,this)">klik-devel@kde.org</a><br><br>To subscribe or \
unsubscribe via the World Wide Web, visit<br> <a \
href="https://mail.kde.org/mailman/listinfo/klik-devel" target="_blank" onclick="return \
top.js.OpenExtLink(window,event,this)"> https://mail.kde.org/mailman/listinfo/klik-devel
</a><br>or, via email, send a message with subject or body 'help' \
to<br> <a \
href="mailto:klik-devel-request@kde.org" target="_blank" onclick="return \
top.js.OpenExtLink(window,event,this)">klik-devel-request@kde.org </a><br><br>You can reach the \
person managing the list at<br> <a \
href="mailto:klik-devel-owner@kde.org" target="_blank" onclick="return \
top.js.OpenExtLink(window,event,this)">klik-devel-owner@kde.org</a><br><br>When replying, \
please edit your Subject line so it is more specific<br> than "Re: Contents of klik-devel \
digest..."<br><br><br>Today's Topics: <br><br> 1. klikutils + recipe.xml \
(Lionel Tricon)<br><br><br>----------------------------------------------------------------------<br><br>Message: \
1<br>Date: Sat, 17 Mar 2007 13:52:37 +0100<br>From: Lionel Tricon < <a \
href="mailto:lionel.tricon@free.fr" target="_blank" onclick="return \
top.js.OpenExtLink(window,event,this)">lionel.tricon@free.fr</a>><br>Subject: [klik-devel] \
klikutils + recipe.xml<br>To: <a href="mailto:klik-devel@kde.org" target="_blank" \
onclick="return top.js.OpenExtLink(window,event,this)"> klik-devel@kde.org</a><br>Message-ID: \
<<a href="mailto:200703171352.37475.lionel.tricon@free.fr" target="_blank" onclick="return \
top.js.OpenExtLink(window,event,this)"> \
200703171352.37475.lionel.tricon@free.fr</a>><br>Content-Type: \
text/plain; charset="iso-8859-1"<br><br>The last available version of \
klikutils use now an xml file to load<br>informations about what have to be run into the cmg \
file (/etc/recipe.xml <br>file located into the cmg file).<br><br>It was inspired by examples \
given on<br><a href="http://klik.atekon.de/wiki/index.php/Klik2" target="_blank" \
onclick="return top.js.OpenExtLink(window,event,this)">http://klik.atekon.de/wiki/index.php/Klik2
</a> and on which i applied slightly<br>modifications.
<br><br>The main section to run the application is located into the runtime section (i<br>used \
SAX to parse this specific section ; all things around can be changed) \
:<br><br><runtime><br> <appname>/usr/bin/ksudoku</appname> \
<br> <apprun>/usr/bin/ksudoku</apprun><br> <env><br> <var \
name="KDE_FORK_SLAVES" \
mode="replace">1</var><br> <var \
name="PATH" mode="append">/usr/bin</var> \
<br> <var name="LD_LIBRARY_PATH" \
mode="append">/usr/lib</var><br> </env><br></runtime><br><br>appname: \
Binary or script to run the application<br>apprun: Binary really started <br><br>To apply a lot \
of modifications onto the environment variables before running<br>the application \
:<br><br>replace: replace the environment variable<br>For example, <var \
name="KDE_FORK_SLAVES" mode="replace">1</var> gives "export \
<br>KDE_FORK_SLAVES=1"<br><br>append: concat the environment variable to the existing \
one<br>For example, <var name="PATH" \
mode="append">/usr/bin</var> fives "export<br>PATH=$PATH:/usr/bin" \
<br><br>unset: unset an existing environment variable<br>For example, <var \
name="FOO" mode="unset"/> gives "unset FOO"<br><br>For \
example, for kdissert, it gives us :<br><br><?xml version=' 1.0' \
encoding='UTF-8'?><br><recipe creation="2007-03-16 10:43" \
version="0.1"><br><br> <name>ksudoku</name><br> <version>0.3-2</version><br> <desc>Sudoku \
puzzle generator/solver</desc> <br> <source><a \
href="http://klik.atekon.de?application=ksudoku" target="_blank" onclick="return \
top.js.OpenExtLink(window,event,this)">http://klik.atekon.de?application=ksudoku</a></source><br> <maintainer>Joe \
Smith</maintainer> <br><br> <system required="LSB3">
<br> <desktop>/usr/share/applnk/Games/ksudoku.desktop</desktop&g \
t;<br> <icons><br> <icon \
type="png" \
size="32"<br>src="/usr/share/icons/hicolor/32x32/apps/ksudoku.png"/> \
<br> </icons><br> </system><br><br> <packages><br><br><package><a \
href="http://ovh.dl.sourceforge.net/sourceforge/ksudoku/ksudoku_0.3-2_i386.deb" target="_blank" \
onclick="return top.js.OpenExtLink(window,event,this)"> \
http://ovh.dl.sourceforge.net/sourceforge/ksudoku/ksudoku_0.3-2_i386.deb \
</a></package><br><br><package><a \
href="ftp://ftp.debian.org/debian/pool/main/n/nas/libaudio2_1.8-3_i386.deb" target="_blank" \
onclick="return top.js.OpenExtLink(window,event,this)">ftp://ftp.debian.org/debian/pool/main/n/nas/libaudio2_1.8-3_i386.deb
</a></package><br> </packages>
<br><br> <runtime><br> <appname>/usr/bin/ksudoku&l \
t;/appname><br> <apprun>/usr/bin/ksudoku</apprun><br> <env><br> <var \
name="KDE_FORK_SLAVES" mode="replace">1</var> \
<br> <var name="PATH" \
mode="append">/usr/bin</var><br> <var \
name="LD_LIBRARY_PATH" \
mode="append">/usr/lib</var><br> </env><br> </runtime>
<br><br></recipe><br><br>I have done a cmg file for bluefish this morning and it works \
perfectly. I<br>have ran at the same time, bluefish, ksudoku, kdissert and OpenOffice \
without<br>worry.<br><br>If you want to test it, remember that you need to call <br>the \
/opt/klikutils/sh/zAppRun script to launch a cmg file in this version.<br><br>What do you think \
?<br><br>Lionel<br><br>On Friday 09 March 2007 16:05:33 Lionel Tricon wrote:<br>> New \
version of the klikutils bundle which brings some interresting features <br>> : - You can \
now relocate the /opt/klikutils directory : You need to specify<br>> it into the -u \
parameter (so you can put the zAppRun script where you want)<br>> - All the wrapper scripts \
are now located outside the cmg file and then can <br>> be modify more easily \
(/opt/klikutils/sh directory)<br>><br>> For the moment, the informations which are used \
to specify what binary<br>> should be run are available in plain text inside the cmg \
file.<br>
><br>> # cat /etc/klik.conf<br>> export \
KLIK_APPNAME="/opt/kde3/bin/kdissert"<br>> export \
KLIK_APPRUN="/opt/kde3/bin/kdissert"<br>> export \
KLIK_APPPATH=":/opt/kde3/bin"<br>> export \
KLIK_APPLIBRARY=":/opt/kde3/lib/kde3" <br>><br>> The job of the \
/opt/klikutils/sh/wrapper.env script is to parse this file<br>> to export all these \
variables.<br>><br>> If the format of the /etc/klik.conf file change in the futur (for \
example, <br>
> for an xml file), we just have to modify this script to parse in a<br>> different way \
the klik.conf file (or an another name if you have a better<br>> idea).<br>><br>> For \
example, we could reuse the following : <br>> <a \
href="http://linuxfromscratch.org/pipermail/alfs-discuss/2006-January/007537.html" \
target="_blank" onclick="return \
top.js.OpenExtLink(window,event,this)">http://linuxfromscratch.org/pipermail/alfs-discuss/2006-January/007537.html
</a><br>><br>> Important to know that the path of the klikutils bundle is added on the \
fly <br>> by fuseiso at the end of the wrapper.env script to export the \
KLIK_BASENAME<br>> variable.<br>><br>> lionel@linux:~> cat \
/opt/klikutils/sh/wrapper.env<br>> test -f /etc/klik.conf && . /etc/klik.conf \
<br>><br>> lionel@linux:~> cat /tmp/app/1/mnt/wrapper.env<br>> test -f \
/etc/klik.conf && . /etc/klik.conf<br>> export \
KLIK_BASENAME=/opt/klikutils<br>><br>> To test it, please go to <a \
href="http://lionel.tricon.free.fr/KLIK/" target="_blank" onclick="return \
top.js.OpenExtLink(window,event,this)">
http://lionel.tricon.free.fr/KLIK/</a> as usual.<br>><br>> I this version, the zAppRun \
script is available directly into<br>> the /opt/klikutils/sh directory.<br>><br>> To \
test the kdissert cmg file in a graphical way under kde, change the <br>> \
~/.kde/share/applnk/.hidden/AppRun.desktop file to change the manner how<br>> zAppRun is \
calling (Exec=/opt/klikutils/sh/zAppRun %U).<br>><br>> The klikutils bundle contains now \
the following :<br>> /opt/klikutils/ <br>> /opt/klikutils/sh<br>> \
/opt/klikutils/sh/wrapper.chroot<br>> /opt/klikutils/sh/wrapper.env<br>> \
/opt/klikutils/sh/zAppRun<br>> /opt/klikutils/sh/wrapper<br>> /opt/klikutils/bin<br>> \
/opt/klikutils/bin/chroot <br>> /opt/klikutils/bin/fuseiso<br>> \
/opt/klikutils/bin/fusermount<br>> /opt/klikutils/lib<br>> \
/opt/klikutils/lib/fakechroot<br>> \
/opt/klikutils/lib/fakechroot/libfakechroot.so<br>><br>> If you have any questions or \
suggestions, don't hesitate to contact me. <br>><br>> \
Lionel<br><br><br><br><br>------------------------------<br><br>_______________________________________________<br>klik-devel \
mailing list<br><a href="mailto:klik-devel@kde.org" target="_blank" onclick="return \
top.js.OpenExtLink(window,event,this)"> klik-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/klik-devel" target="_blank" onclick="return \
top.js.OpenExtLink(window,event,this)">https://mail.kde.org/mailman/listinfo/klik-devel</a><br><br><br>End \
of klik-devel Digest, Vol 14, Issue 3 \
<br>*****************************************<br></blockquote> </div><br>
</span></div></blockquote></div><br>
_______________________________________________
klik-devel mailing list
klik-devel@kde.org
https://mail.kde.org/mailman/listinfo/klik-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic