[prev in list] [next in list] [prev in thread] [next in thread]
List: klik-devel
Subject: Re: [klik-devel] klik-devel Digest, Vol 15, Issue 1
From: "Jason Taylor" <killerkiwi2005 () gmail ! com>
Date: 2007-04-02 9:21:30
Message-ID: 94dd8f6f0704020221q2c36573i8d2bbffba582588b () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
More random thoughts... should we approach the guy(s?) who wrote zero
install about merging the 2 techniques... really what we are doing is
creating zero install into a single file and making it executable... the
projects seem (to me any way) very similar at this point.
KillerKiwi
On 4/2/07, Jason Taylor <killerkiwi2005@gmail.com> wrote:
>
> This is looking very nice :)
>
> The ROX format does look good and as a bonus it has some nice GUI tools
> http://0install.net/injector-packagers.html
>
> It needs a few extras but we get 95% there for free
>
> WIki page
> http://klik.atekon.de/wiki/index.php/Recipe_Files
>
> Later
>
> Killerkiwi
>
>
>
>
> On 4/1/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. fusecram now part of the klikutils bundle (Lionel Tricon)
> > 2. Testing Klik (Alexey Eremenko)
> > 3. Re: Testing Klik (lionel.tricon@free.fr )
> > 4. Re: Testing Klik (Alexey Eremenko)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Sat, 31 Mar 2007 14:09:51 +0200
> > From: Lionel Tricon < lionel.tricon@free.fr>
> > Subject: [klik-devel] fusecram now part of the klikutils bundle
> > To: klik-devel@kde.org
> > Message-ID: < 200703311409.51742.lionel.tricon@free.fr>
> > Content-Type: text/plain; charset="us-ascii"
> >
> > Hello,
> >
> > Some news about klikutils :
> > - fusecram is now available inside the bundle so you can use both
> > isofs/cramfs
> > cmg files now
> > - both fuseiso and fusecram share now the same source code which is much
> > more
> > modular that the old one i wrote - that should ease the development and
> > maintenance since, except the code wrote by Dmitry, all the rest is
> > common
> > (klikutils-fuse-20070331.tgz available on my web site)
> > - i use now pidof into the wrapper script to check if the application is
> > running since i faced some troubles with the use of the use_ino option
> > with
> > fuse (strange crash with OOo even if it works for all others
> > applications)
> > - and i remember that now klikutils is relocatable, can redirect writes
> > (need
> > to be testing more intensively), use actually a single xml configuration
> > file
> > and need only the fuse module to be running (the libfuse is hard linked)
> >
> > - all wrapper* files located into the /opt/klikutils/sh directory
> > appears
> > automaticaly at the root of the mount cmg file ; i can hide them since
> > you
> > still access files even if they are not listed into a directory (i just
> > need
> > to comment some lines into the source code)
> >
> > You would find some cmg files (both iso/cram) on
> > http://lionel.tricon.free.fr/KLIK if you want to test it. Wiki pages are
> > up
> > to date.
> >
> > Now that this solution is working (at least for me, on my own
> > plateform),
> > maybe it could be interresting to determine what should be done now and
> > who
> > can do the job. A roadmap could be a good idea.
> >
> > I think mainly about :
> > - xml file format (the row file format seems promising)
> > - Thumbnails / Icons (Fabianx seems to have produced a part of the job
> > to
> > extract the image from the cmg file)
> > - display metadata of a cmg file (we only need to extract the xml file
> > and
> > integrate date into kde/gnome)
> > - test mountlo to redirect writes into an iso file thanks to fuse
> >
> > Even if an another virtualization option appears in the futur to be a
> > better
> > solution that this one based exclusively on fuse, all the others parts
> > will
> > be ready (even i think that this one make sense ...).
> >
> > And what about GSOC ? I read some informations on the wiki pages but i
> > found
> > nothing on http://code.google.com/soc/ ...
> >
> > Lionel
> >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Sat, 31 Mar 2007 22:56:03 +0200
> > From: "Alexey Eremenko" <al4321@gmail.com>
> > Subject: [klik-devel] Testing Klik
> > To: klik-devel@kde.org
> > Message-ID:
> > <7fac565a0703311356g120f6b80vb499aa4780bcb7c2@mail.gmail.com >
> > Content-Type: text/plain; charset=UTF-8; format=flowed
> >
> > hi all !
> >
> > What's the best way to BETA-test klik ?
> > maybe we can write some script, that manages to start & close klik
> > apps automatically ?
> > This way we could test it on many distro's at the same time.
> >
> > If not, then' we can only BETA-test by hand. :( - which will
> > effectively limit us to few OSes and packages.
> >
> > --
> > -Alexey Eremenko "Technologov"
> >
> >
> > ------------------------------
> >
> > Message: 3
> > Date: Sat, 31 Mar 2007 23:22:54 +0200
> > From: lionel.tricon@free.fr
> > Subject: Re: [klik-devel] Testing Klik
> > To: Alexey Eremenko <al4321@gmail.com>
> > Cc: klik-devel@kde.org
> > Message-ID: < 1175376174.460ed12eb952b@imp.free.fr>
> > Content-Type: text/plain; charset=ISO-8859-1
> >
> > Selon Alexey Eremenko <al4321@gmail.com>:
> > > What's the best way to BETA-test klik ?
> > > maybe we can write some script, that manages to start & close klik
> > > apps automatically ?
> > > This way we could test it on many distro's at the same time.
> >
> > If you want to test a cmg file by hand :
> > ${KLIKUTILS_PATH}/sh/zAppRun
> > /home/lionel/Desktop/pdfedit-20070324_cramfs.cmg
> >
> > if the application crash, the previous command will fail quickly. Maybe
> > we can
> > write a script which run a list of cmg files ; for each file, we run it
> > and wait
> > it to fail within 30 seconds ; else, we consider that the application is
> > working
> > good, we kill it and go through the next one.
> >
> > Lionel
> >
> >
> > ------------------------------
> >
> > Message: 4
> > Date: Sat, 31 Mar 2007 23:31:58 +0200
> > From: "Alexey Eremenko" <al4321@gmail.com>
> > Subject: Re: [klik-devel] Testing Klik
> > To: klik-devel@kde.org
> > Message-ID:
> > <7fac565a0703311431w30511570j233553f43bc7fac1@mail.gmail.com>
> > Content-Type: text/plain; charset=UTF-8; format=flowed
> >
> > > If you want to test a cmg file by hand :
> > > ${KLIKUTILS_PATH}/sh/zAppRun
> > /home/lionel/Desktop/pdfedit-20070324_cramfs.cmg
> > >
> > > if the application crash, the previous command will fail quickly.
> > Maybe we can
> > > write a script which run a list of cmg files ; for each file, we run
> > it and wait
> > > it to fail within 30 seconds ; else, we consider that the application
> > is working
> > > good, we kill it and go through the next one.
> > >
> >
> > Such a script will be of hi-value, due to "alpha" quality of some
> > packages on certain distros.
> >
> > While openSUSE seems to perform mostly OK, Fedora crashes left and
> > right.... While I'm not a Fedora user myself, I'm interested in
> > getting better stability overall (and I have FC4 DVD lying around...)
> >
> > --
> > -Alexey Eremenko "Technologov"
> >
> >
> > ------------------------------
> >
> > _______________________________________________
> > klik-devel mailing list
> > klik-devel@kde.org
> > https://mail.kde.org/mailman/listinfo/klik-devel
> >
> >
> > End of klik-devel Digest, Vol 15, Issue 1
> > *****************************************
> >
>
>
[Attachment #5 (text/html)]
More random thoughts... should we approach the guy(s?) who wrote zero install about \
merging the 2 techniques... really what we are doing is creating zero install into a \
single file and making it executable... the projects seem (to me any way) very \
similar at this point. <br><br>KillerKiwi<br><br><div><span class="gmail_quote">On \
4/2/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;"> This is looking very nice \
:)<br><br>The ROX format does look good and as a bonus it has some nice GUI \
tools<br><a href="http://0install.net/injector-packagers.html" target="_blank" \
onclick="return top.js.OpenExtLink(window,event,this)"> \
http://0install.net/injector-packagers.html</a><br><br>It needs a few extras but we \
get 95% there for free <br><br>WIki page<br><a \
href="http://klik.atekon.de/wiki/index.php/Recipe_Files" target="_blank" \
onclick="return top.js.OpenExtLink(window,event,this)">http://klik.atekon.de/wiki/index.php/Recipe_Files</a><br><br>Later<br>
<br>Killerkiwi<div><span class="e" \
id="q_111b1907066e4a68_1"><br><br><br><br><br><div><span class="gmail_quote">On \
4/1/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. fusecram now part of the klikutils bundle (Lionel \
Tricon)<br> 2. Testing Klik (Alexey Eremenko)<br> 3. Re: \
Testing Klik (<a href="mailto:lionel.tricon@free.fr" target="_blank" onclick="return \
top.js.OpenExtLink(window,event,this)"> lionel.tricon@free.fr
</a>)<br> 4. Re: Testing Klik (Alexey \
Eremenko)<br><br><br>----------------------------------------------------------------------<br><br>Message: \
1<br>Date: Sat, 31 Mar 2007 14:09:51 +0200<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] fusecram now part of the \
klikutils bundle<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:200703311409.51742.lionel.tricon@free.fr" \
target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> \
200703311409.51742.lionel.tricon@free.fr</a>><br>Content-Type: \
text/plain; charset="us-ascii"<br><br>Hello,<br><br>Some news \
about klikutils :<br>- fusecram is now available inside the bundle so you can use \
both isofs/cramfs <br>cmg files now<br>- both fuseiso and fusecram share now the same \
source code which is much more<br>modular that the old one i wrote - that should ease \
the development and<br>maintenance since, except the code wrote by Dmitry, all the \
rest is common <br>(klikutils-fuse-20070331.tgz available on my web site)<br>- i use \
now pidof into the wrapper script to check if the application is<br>running since i \
faced some troubles with the use of the use_ino option with<br>fuse (strange crash \
with OOo even if it works for all others applications) <br>- and i remember that now \
klikutils is relocatable, can redirect writes (need<br>to be testing more \
intensively), use actually a single xml configuration file<br>and need only the fuse \
module to be running (the libfuse is hard linked) <br>- all wrapper* files located \
into the /opt/klikutils/sh directory appears<br>automaticaly at the root of the mount \
cmg file ; i can hide them since you<br>still access files even if they are not \
listed into a directory (i just need <br>to comment some lines into the source \
code)<br><br>You would find some cmg files (both iso/cram) on<br><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> if you \
want to test it. Wiki pages are up <br>to date.<br><br>Now that this solution is \
working (at least for me, on my own plateform),<br>maybe it could be interresting to \
determine what should be done now and who<br>can do the job. A roadmap could be a \
good idea. <br><br>I think mainly about :<br>- xml file format (the row file format \
seems promising)<br>- Thumbnails / Icons (Fabianx seems to have produced a part of \
the job to<br>extract the image from the cmg file)<br>- display metadata of a cmg \
file (we only need to extract the xml file and <br>integrate date into \
kde/gnome)<br>- test mountlo to redirect writes into an iso file thanks to \
fuse<br><br>Even if an another virtualization option appears in the futur to be a \
better<br>solution that this one based exclusively on fuse, all the others parts will \
<br>be ready (even i think that this one make sense ...).<br><br>And what about GSOC \
? I read some informations on the wiki pages but i found<br>nothing on <a \
href="http://code.google.com/soc/" target="_blank" onclick="return \
top.js.OpenExtLink(window,event,this)"> http://code.google.com/soc/
</a> ...<br><br>Lionel<br><br><br>------------------------------<br><br>Message: \
2<br>Date: Sat, 31 Mar 2007 22:56:03 +0200<br>From: "Alexey Eremenko" \
<<a href="mailto:al4321@gmail.com" target="_blank" onclick="return \
top.js.OpenExtLink(window,event,this)"> al4321@gmail.com</a>>
<br>Subject: [klik-devel] Testing Klik<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:<br> <<a \
href="mailto:7fac565a0703311356g120f6b80vb499aa4780bcb7c2@mail.gmail.com" \
target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> \
7fac565a0703311356g120f6b80vb499aa4780bcb7c2@mail.gmail.com </a>><br>Content-Type: \
text/plain; charset=UTF-8; format=flowed<br><br>hi all !<br><br>What's the best \
way to BETA-test klik ?<br>maybe we can write some script, that manages to start \
& close klik<br>apps automatically ? <br>This way we could test it on many \
distro's at the same time.<br><br>If not, then' we can only BETA-test by \
hand. :( - which will<br>effectively limit us to few OSes and \
packages.<br><br>--<br>-Alexey Eremenko "Technologov" \
<br><br><br>------------------------------<br><br>Message: 3<br>Date: Sat, 31 Mar \
2007 23:22:54 +0200<br>From: <a href="mailto:lionel.tricon@free.fr" target="_blank" \
onclick="return top.js.OpenExtLink(window,event,this)"> \
lionel.tricon@free.fr</a><br>Subject: Re: [klik-devel] Testing \
Klik<br>
To: Alexey Eremenko <<a href="mailto:al4321@gmail.com" target="_blank" \
onclick="return top.js.OpenExtLink(window,event,this)">al4321@gmail.com</a>><br>Cc: \
<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:1175376174.460ed12eb952b@imp.free.fr" target="_blank" onclick="return \
top.js.OpenExtLink(window,event,this)"> \
1175376174.460ed12eb952b@imp.free.fr</a>><br>Content-Type: text/plain; \
charset=ISO-8859-1<br><br>Selon Alexey Eremenko <<a href="mailto:al4321@gmail.com" \
target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> \
al4321@gmail.com</a>>:<br>> What's the best way to BETA-test klik ? \
<br>> maybe we can write some script, that manages to start & close \
klik<br>> apps automatically ?<br>> This way we could test it on many \
distro's at the same time.<br><br>If you want to test a cmg file by hand : \
<br>${KLIKUTILS_PATH}/sh/zAppRun \
/home/lionel/Desktop/pdfedit-20070324_cramfs.cmg<br><br>if the application crash, the \
previous command will fail quickly. Maybe we can<br>write a script which run a list \
of cmg files ; for each file, we run it and wait <br>it to fail within 30 seconds ; \
else, we consider that the application is working<br>good, we kill it and go through \
the next one.<br><br>Lionel<br><br><br>------------------------------<br><br>Message: \
4<br>Date: Sat, 31 Mar 2007 23:31:58 +0200 <br>From: "Alexey Eremenko" \
<<a href="mailto:al4321@gmail.com" target="_blank" onclick="return \
top.js.OpenExtLink(window,event,this)">al4321@gmail.com</a>><br>Subject: Re: \
[klik-devel] Testing Klik<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:
<br> <<a \
href="mailto:7fac565a0703311431w30511570j233553f43bc7fac1@mail.gmail.com" \
target="_blank" onclick="return \
top.js.OpenExtLink(window,event,this)">7fac565a0703311431w30511570j233553f43bc7fac1@mail.gmail.com
</a>><br>Content-Type: text/plain; charset=UTF-8; format=flowed<br>
<br>> If you want to test a cmg file by hand :<br>> \
${KLIKUTILS_PATH}/sh/zAppRun \
/home/lionel/Desktop/pdfedit-20070324_cramfs.cmg<br>><br>> if the application \
crash, the previous command will fail quickly. Maybe we can <br>> write a script \
which run a list of cmg files ; for each file, we run it and wait<br>> it to fail \
within 30 seconds ; else, we consider that the application is working<br>> good, \
we kill it and go through the next one. <br>><br><br>Such a script will be of \
hi-value, due to "alpha" quality of some<br>packages on certain \
distros.<br><br>While openSUSE seems to perform mostly OK, Fedora crashes left \
and<br>right.... While I'm not a Fedora user myself, I'm interested in \
<br>getting better stability overall (and I have FC4 DVD lying \
around...)<br><br>--<br>-Alexey Eremenko \
"Technologov"<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 15, Issue 1 \
<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