On Mon, 2003-03-03 at 22:00, Vox wrote: > This time James Sparenberg <[EMAIL PROTECTED]> > becomes daring and writes: > > > On Mon, 2003-03-03 at 09:10, Guillaume Cottenceau wrote: > >> Helge Hielscher <[EMAIL PROTECTED]> writes: > >> > >> > -rpmdrake: > >> > *proxy configuration is not easy and is not explained in the help > >> > file (how to use a ftp and an http proxy?) > >> > >> Well I don't know myself very much on how to use both types of > >> proxies :). > >> > >> I guess this feature is, first, for experts and second, I need > >> suggestions and tests by users to ameliorate it. > >> > >> > *the UI is sometimes very slow > >> > *difficult to add a cooker source (there need to be some help > >> > with synthesis/hdlist) > >> > >> The list of cooker sources has been deliberately removed because > >> people used to use cooker for "updating their packages", that > >> leading with broken systems. > > > > Two questions here. > > > > 1. Doesn't this violate the GPL > > No
Now I know. > > > 2. Don't try to protect people from themselves, it only causes ill > > will. > > Uhm...when I noticed they had done this, I didn't think they were > protecting people from themselves...I thought "smart guys, they are > protecting whoever has to deal with tech support"...try to deal with > a user that broke his box by using cooker as an "update" media > without knowing what cooker really is. > Which is why I said... Ultimately it's their distro.... Downside... it makes it darn difficult for me to find out if my problem is a bug per se or a conflict with my hardware etc. For example: the new QT3 libs in cooker stop kde from working on my laptop... but if I move back to the ones in RC1... it works fine. But since no one else is reporting this I'd love to know why it's happening for me. Without the data ... it's hard to do. > Vox
