[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 8
From: "Jason Taylor" <killerkiwi2005 () gmail ! com>
Date: 2007-04-23 21:20:07
Message-ID: 94dd8f6f0704231420k717c09d9s8d7a0e50d12c0b41 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
YES. we should use the ROX format... main advantage is the tools that
already exist that we can borrow from zero-install with 90% of the work is
already done.
I've been meaning to get a klik version of the zero-install up and running
but got distracted by my new mythtv box :)
From my quick browse through the python code it really just looks like a
matter of removing all the stuff we don't need.... and some re factoring
Subversion Repo - http://sourceforge.net/svn/?group_id=76468.
Where should we go from here.....
1) Identify which parts of ROX we need to extend - Not much I think
2) Tweak Lionel's code to use the ROX format + klik extensions
3) Use the existing zero-install code as a base to build a new python klik
client
4) Change the server to generate ROX xml for the new client
5) Consider backwards compatibility with existing klik packages - Is this a
major consideration?
6) Consider building packages at least an RPM and a DEB
Killerkiwi
On 4/23/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. recipe file format (lionel.tricon@free.fr)
> 2. Re: recipe file format (Alexey Eremenko)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 22 Apr 2007 19:50:11 +0200
> From: lionel.tricon@free.fr
> Subject: [klik-devel] recipe file format
> To: klik-devel@kde.org
> Message-ID: <1177264211.462ba0534c0ed@imp.free.fr>
> Content-Type: text/plain; charset=ISO-8859-1
>
>
> Hello,
>
> Did someone have any news about the recipe file definition ? Since we can
> borrow
> large part of the rox file format and that we have some ideas on how we
> want to
> use it (consequentlty, how to modify it to fit our need), it appears to me
> that
> i could be very easy to specify an almost final version in few days if we
> really
> want to. It could be a good way to re-inject enthusiasm into this project
> since
> a lot a things are based on the availability of this file format.
>
> Lionel
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 23 Apr 2007 03:55:11 +0100
> From: "Alexey Eremenko" <al4321@gmail.com>
> Subject: Re: [klik-devel] recipe file format
> To: klik-devel@kde.org
> Message-ID:
> <7fac565a0704221955w261a789di2dd03a63a1e3ca74@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> On 4/22/07, lionel.tricon@free.fr <lionel.tricon@free.fr> wrote:
> >
> > Hello,
> >
> > Did someone have any news about the recipe file definition ? Since we
> can borrow
> > large part of the rox file format and that we have some ideas on how we
> want to
> > use it (consequentlty, how to modify it to fit our need), it appears to
> me that
> > i could be very easy to specify an almost final version in few days if
> we really
> > want to. It could be a good way to re-inject enthusiasm into this
> project since
> > a lot a things are based on the availability of this file format.
> >
> > Lionel
>
> 1. I don't really ever heard of the rox format.
>
> 2. If we building new recipe file, it would be good to make it
> compatible with several klik-clients (normal/FUSE/etc...) and a new
> feature that I would like to see is "source recipe" - that is a file
> that downloads upstream source code, and then builds on the target
> machine, similar to ArchLinux (and maybe Gentoo).
> The latter will give more flexibility to klik.
>
>
> --
> -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 8
> *****************************************
>
[Attachment #5 (text/html)]
YES. we should use the ROX format... main advantage is the tools that already exist that we can \
borrow from zero-install with 90% of the work is already done.<br><br>I've been meaning to \
get a klik version of the zero-install up and running but got distracted by my new mythtv box \
:) <br><br>From my quick browse through the python code it really just looks like a matter of \
removing all the stuff we don't need.... and some re factoring<br>Subversion Repo - <a \
href="http://sourceforge.net/svn/?group_id=76468"> \
http://sourceforge.net/svn/?group_id=76468</a>.<br><br>Where should we go from here.....<br>1) \
Identify which parts of ROX we need to extend - Not much I think<br>2) Tweak Lionel's code \
to use the ROX format + klik extensions <br>3) Use the existing zero-install code as a base to \
build a new python klik client<br>4) Change the server to generate ROX xml for the new \
client<br>5) Consider backwards compatibility with existing klik packages - Is this a major \
consideration? <br>6) Consider building packages at least an RPM and a \
DEB<br><br><br>Killerkiwi<br><br><br><br><br><div><span class="gmail_quote">On 4/23/07, <b \
class="gmail_sendername"><a href="mailto:klik-devel-request@kde.org">klik-devel-request@kde.org \
</a></b> <<a href="mailto:klik-devel-request@kde.org">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">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"> \
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">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">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. recipe file format (<a \
href="mailto:lionel.tricon@free.fr">lionel.tricon@free.fr</a>)<br> 2. Re: recipe \
file format (Alexey Eremenko)<br><br><br>----------------------------------------------------------------------
<br><br>Message: 1<br>Date: Sun, 22 Apr 2007 19:50:11 +0200<br>From: <a \
href="mailto:lionel.tricon@free.fr">lionel.tricon@free.fr</a><br>Subject: [klik-devel] recipe \
file format<br>To: <a href="mailto:klik-devel@kde.org"> klik-devel@kde.org</a><br>Message-ID: \
<<a href="mailto:1177264211.462ba0534c0ed@imp.free.fr">1177264211.462ba0534c0ed@imp.free.fr</a>><br>Content-Type: \
text/plain; charset=ISO-8859-1<br><br><br>Hello,<br><br>Did someone have any news about the \
recipe file definition ? Since we can borrow <br>large part of the rox file format and that we \
have some ideas on how we want to<br>use it (consequentlty, how to modify it to fit our need), \
it appears to me that<br>i could be very easy to specify an almost final version in few days if \
we really <br>want to. It could be a good way to re-inject enthusiasm into this project \
since<br>a lot a things are based on the availability of this file \
format.<br><br>Lionel<br><br><br>------------------------------<br><br>Message: 2 <br>Date: \
Mon, 23 Apr 2007 03:55:11 +0100<br>From: "Alexey Eremenko" <<a \
href="mailto:al4321@gmail.com">al4321@gmail.com</a>><br>Subject: Re: [klik-devel] recipe \
file format<br>To: <a href="mailto:klik-devel@kde.org"> \
klik-devel@kde.org</a><br>Message-ID:<br> <<a \
href="mailto:7fac565a0704221955w261a789di2dd03a63a1e3ca74@mail.gmail.com">7fac565a0704221955w261a789di2dd03a63a1e3ca74@mail.gmail.com</a>><br>Content-Type: \
text/plain; charset=UTF-8; format=flowed <br><br>On 4/22/07, <a \
href="mailto:lionel.tricon@free.fr">lionel.tricon@free.fr</a> <<a \
href="mailto:lionel.tricon@free.fr">lionel.tricon@free.fr</a>> wrote:<br>><br>> \
Hello,<br>><br>> Did someone have any news about the recipe file definition ? Since we \
can borrow <br>> large part of the rox file format and that we have some ideas on how we \
want to<br>> use it (consequentlty, how to modify it to fit our need), it appears to me \
that<br>> i could be very easy to specify an almost final version in few days if we really \
<br>> want to. It could be a good way to re-inject enthusiasm into this project \
since<br>> a lot a things are based on the availability of this file format.<br>><br>> \
Lionel<br><br>1. I don't really ever heard of the rox format. <br><br>2. If we building new \
recipe file, it would be good to make it<br>compatible with several klik-clients \
(normal/FUSE/etc...) and a new<br>feature that I would like to see is "source recipe" \
- that is a file <br>that downloads upstream source code, and then builds on the \
target<br>machine, similar to ArchLinux (and maybe Gentoo).<br>The latter will give more \
flexibility to klik.<br><br><br>--<br>-Alexey Eremenko "Technologov" \
<br><br><br>------------------------------<br><br>_______________________________________________<br>klik-devel \
mailing list<br><a href="mailto:klik-devel@kde.org">klik-devel@kde.org</a><br><a \
href="https://mail.kde.org/mailman/listinfo/klik-devel"> \
https://mail.kde.org/mailman/listinfo/klik-devel</a><br><br><br>End of klik-devel Digest, Vol \
15, Issue 8<br>*****************************************<br></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