From klik-devel Mon Apr 23 21:20:07 2007 From: "Jason Taylor" Date: Mon, 23 Apr 2007 21:20:07 +0000 To: klik-devel Subject: Re: [klik-devel] klik-devel Digest, Vol 15, Issue 8 Message-Id: <94dd8f6f0704231420k717c09d9s8d7a0e50d12c0b41 () mail ! gmail ! com> X-MARC-Message: https://marc.info/?l=klik-devel&m=117736326005364 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============1544287137==" --===============1544287137== Content-Type: multipart/alternative; boundary="----=_Part_194341_20680353.1177363207152" ------=_Part_194341_20680353.1177363207152 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 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" > 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 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 > ***************************************** > ------=_Part_194341_20680353.1177363207152 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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
*****************************************

------=_Part_194341_20680353.1177363207152-- --===============1544287137== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ klik-devel mailing list klik-devel@kde.org https://mail.kde.org/mailman/listinfo/klik-devel --===============1544287137==--