<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Richard Hughes wrote:
<blockquote cite="mid:1192636352.2842.2.camel@hughsie-laptop"
type="cite">
<pre wrap="">On Wed, 2007-10-17 at 10:13 -0400, Robin Norwood wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Tim Lauridsen <a class="moz-txt-link-rfc2396E" href="mailto:tla@rasmil.dk"><tla@rasmil.dk></a> writes:
</pre>
<blockquote type="cite">
<pre wrap="">Richard Hughes wrote:
</pre>
<blockquote type="cite">
<pre wrap="">"get-repo-list.py" should return:
repo-detail<tab>fedora-development-debuginfo<tab>Fedora Development (debug)<tab>true
</pre>
</blockquote>
<pre wrap="">this sounds fine to me, it is easy to implement
</pre>
<blockquote type="cite">
<pre wrap="">and "repo-enable.py fedora-development-debuginfo false" should disable
the repo. We don't have to do anything with repo-set-data.py yet, we
need to think about what is allowed, and what would make sense to
abstract.
</pre>
</blockquote>
<pre wrap="">There is an issue here, here is no persistence between the calls to
the different yum helpers, so for this to work we have some choices to
make.
1. repo-enable changes the repo enabled permanent by changing the
enabled=' in there *.repo files. (UGLY)
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
This is what we should do.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">2. write the packagekit repo state to some kind of conf file and make
the helpers read and set the repo states from the conf file.
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
Nope, because then we have to keep them in sync - and the user could get
a different experience from a yum install and a pkcon install?
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">3. add a repolist parameter to all helpers.
I prefer 2.
</pre>
</blockquote>
<pre wrap="">I don't know if I agree with that...it means the repos enabled for PK
will be different than for the other package management system (yum, or
whatever). I realize we should play nice with the existing tools, but
if PK is intended to become a replacement frontend, then it seems ok to
me for PK to change their configuration.
</pre>
</blockquote>
<pre wrap=""><!---->
Totally agree. PK should just edit the enabled= line.
Richard.
</pre>
</blockquote>
Ok, i will implement it that way.<br>
<br>
Tim<br>
<br>
</body>
</html>