Re: Was GNUstep ready for GNUstep ?

[address@hidden]

> > release that included the following information for all  
> > applications and frameworks:
> >    Package Name
> >    Latest Version
> >    Release Date
> >    Primary Maintainer (None if package is not actively maintained)
> >    Verified Working With This Core Release? (Yes/No)
> >     Platforms Tested
>
> "flagship" applications from the unusable ones.  The table proposed  
> above was intended to provide an aid for this task.  Without  

IMHO such a table should be kept in a machine readable form on a
project database server so that an Installer.app can access it and
find out what is new and which dependencies are there.

Unfortunately, there is no single package manager out there for e.g.
GNU/Linux,  MacOS X and FreeBSD. Each distribution has its own one -
and is more or less defined by the package manager... apt, ipkg, fink,
macports, open embedded just to name some.

A straightforward way would be to provide package definitions to all
those distributions... But defining and maintaining the three most
important ones is very difficult.

So, the solution must be independent of the OS distribution but
generic to GNUstep.

... volunteers welcome for an Installer.app plus a database.

-- hns