[Fedora-livecd-list] patch review and move of livecd scm

[Jesse Keating]

On Tuesday 06 March 2007 16:38:09 David Zeuthen wrote:
> For testing, I just have a script that invokes the tool with my chosen
> command line options e.g. my local repositories.

I do too, my chosen URLs being in the config file (:

> Also, we can add more sugar to the programs as needed, e.g. perhaps
> interactively prompt for the user to add repositories, make the program
> use a mirror list, add an option to use the default repos for release N,
> use the repos that is specified as active in /etc/yum.repos.d (or
> elsewhere)  etc. etc.

Wouldn't that kind of suger be best in a graphical UI?  You'd want the backend 
to be straight and simple, with interactiveness built into a gui app that 
calls things from the backend, that way you could have a gui gtk front end, a 
web front end, etc...

> > For that reason, the config files I'd stash in there would be genericized
> > to point at say the mirror list for Core and Extras, whereas the one used
> > internally may point to an internal mirror, or something like that.
>
> Ugh, that sounds really painful. I think, in general, the main point is
> that we don't want the users to edit these files, we want users to trade
> such files with each other and so forth.
>
> I guess, to illustrate my point, what I like to be able to
>
>  # livecd-creator --config=http://foo.bar/rawhide/livecd-desktop.ks
>                   --repo=dev,file:///Repos/core
>                   --repo=dev,file:///Repos/extras
>
>  # livecd-creator --config=http://foo.bar/rawhide/livecd-desktop.ks
>                   --use-system-repos
>
>  # livecd-creator --config=http://foo.bar/rawhide/livecd-desktop.ks
>                   --use-repos-from=~/repos/local-rawhide.d
>
>  # livecd-creator --config=http://foo.bar/6/livecd-desktop.ks
>                   --use-repos-from=~/repos/local-fc6.d
>
> to spin a live cd. Hope this clarifies.

I get what you're saying, but if the common example is using core and extras 
repos, why not default to those in a config file?  I can see adding the 
ability to override that at the cli, and maybe I'll do that for pungi at some 
point, but what I expect people to trade around or fiddle with for pungi is 
the package set, and the name.  A shared config that everybody uses doesn't 
strike me as useful if everybody is just creating the same thing.  I want 
people to create something different and that requires changing the 
configuration.

-- 
Jesse Keating
Release Engineer: Fedora
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-livecd-list/attachments/20070306/401bbfa2/attachment.sig>