Ainsi parlait Chad :
> 3)The final suggestion I have is for the creation of an App called
> something like drakecooker or cookerdrake. This would be a program for
> helping with cooker testing. A gui or commandline interface which could
> control updateing the cooker installation. Allowing users to choose when
> and what parts of cooker they wanted to update and set up cron jobs to do
> it.
> -It would report/list what packages had been updated after runing the
> update cooker command and list the changes made to them (scan the changelog
> in the spec file).
> - List requests for moreinfo on bugs and specific requests for testing of
> new or updated packages.
> It would be closely tied to bugdrake allowing easy bug reporting etc.
> -report bugs in areas of interest. So you could tell it you wanted to
> mainly test Multimedia pacakges it would then list new, needinfo and
> unresolved bugs from the mulitmedia packages section that you could have a
> look at, test etc. - and have a package/cvs upload front end for uploading
> changes or patches.
Cooker is supposed to be an experimental distribution, higly instable, not
meant for everyday use. If you're using it, you're supposed to be some kind
of unix guru able to recover your hard disk the day when booting won't work
anymore.
More and more users forget about this, and would like to benefit from the
bleeding edge applications available in cooker without suffering any risk.
Moreover, they want gui because command-line is too difficult to use, and
documentation to hard to read. That's a misunderstanding of cooker purpose
IMHO.
Investing time and resource for improving cooker usability is a non-sense, not
because we want to stay l337, but because those resource would be more useful
for other purposes. Of course, we could discuss of what kind of improvement,
but GUIs are definitevely too much work, and there is nothing in your list
that could not be solved by some trivial script.
--
Disks are always full. It is futile to try to get more disk space. Data
expands to fill any void.
-- Murphy's Computer Laws n°4
