<!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:1192321050.4186.4.camel@hughsie-laptop"
type="cite">
<pre wrap="">On Sat, 2007-10-13 at 17:12 -0700, Richard Hughes wrote:
</pre>
<blockquote type="cite">
<pre wrap="">+ <row>
+ <entry>Get Repo List</entry>
+ <entry><literal>get-repo-list.*</literal></entry>
+ </row>
+ <row>
+ <entry>Repo Enable</entry>
+ <entry><literal>repo-enable.*</literal></entry>
+ </row>
+ <row>
+ <entry>Repo Set Data</entry>
+ <entry><literal>repo-set-data.*</literal></entry>
+ </row>
</pre>
</blockquote>
<pre wrap=""><!---->
Backend dudes: do you think this will be okay? For yum I'm guessing it
would be quite easy;
"get-repo-list.py" should return:
repo-detail<tab>fedora-development-debuginfo<tab>Fedora Development (debug)<tab>true
</pre>
</blockquote>
this sounds fine to me, it is easy to implement<br>
<blockquote cite="mid:1192321050.4186.4.camel@hughsie-laptop"
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>
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.<br>
1. repo-enable changes the repo enabled permanent by changing the
'enabled=' in there *.repo files. (UGLY)<br>
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.<br>
3. add a repolist parameter to all helpers. <br>
<br>
I prefer 2.<br>
<br>
Comments.<br>
<br>
Tim<br>
<br>
<br>
</body>
</html>