--- Stephen Williams <[EMAIL PROTECTED]> wrote:
> People (other then the overworked developers) need to take on
> the task of making packages. Pre-packaging for common target systems
> is the answer. The developers don't have the time or resources
> to do this, so reliable volunteers (or paid organizations) need
> to take this on.
I agree with Stephen fully. As a debian user everything that
is required is already taken care of for you given a .deb package
is created - external and internal dependencies are all taken
care of, etc. Giving or pointing a new user (newbie) a .deb,
given he's using a debian-derived distro, is the simplest thing
one can possibly do (those .deb packages need to be maintained
and there-in is the issue). The packages noted currently in
debian's APT repository are dated '20040111' (created by Hamish
Moffatt <hamish _at_ debian *dot* org>), so they need to be updated
but I honestly think this might be a good first step. Automate
this process (and it should be easy now since this has already
been done once), upload the debian build scripts to the application's
CVS tree, make this a normal requirement on all current and future
sub-projects and you've accomplished your goal of making getting and
installing gEDA applications a very simple task for new users.
Regards,
.tf.
__________________________________
Do you Yahoo!?
The all-new My Yahoo! - What will yours do?
http://my.yahoo.com
