[IAEP] Sugar platform overview

Aleksey Lim alsroot at member.fsf.org
Tue Jan 6 04:46:52 EST 2009

On Tue, Jan 06, 2009 at 10:18:51AM +0100, Tomeu Vizoso wrote:
> On Tue, Dec 30, 2008 at 08:27, Aleksey Lim <alsroot at member.fsf.org> wrote:
> >
> > I think having central [meta-db] has many benefits:
> > - collaboration: everybody works in one "trunk"
> >  not doing the same work while packaging sugar for various distros
> >  patches/content could be moved from [backends] level to [meta-db] level
> >  and everybody could benefit from that
> > - flexibility: we could choose any format for sugar packaging,
> >  it needs only proper templates
> > - central db is the simplest way to discover sugar and adding new components
> >
> > Note:
> > http://sugarlabs.org/go/DeploymentTeam/jhconvert
> > could be considered as one of the possible prototypes
> Sounds good to me if packagers think that will help them. Though I'm
> not sure who would maintain such db? The packaging teams themselves?
packaging teams I think, and thats not tracking dependencies from scratch -
there is jhbuild's imports, only maintaining stuff thats valuable from
packagers point of view (for example jhbuild could rely on existence of
one package and thats not true in case of specific distro).
Moreover tracking dependencies is only one part of meta info

> Do you know of any other upstream project that has such a facility?
cant say something


More information about the IAEP mailing list