On 26/07/06, Goneri Le Bouder <goneri@rulezlan.org> wrote:
> > On 26/07/06, Eddy PetriÅŸor <eddy.petrisor@gmail.com> wrote:
> > What do you think?
> > Do we have a spare machine to do this. I could do most of the things
> > for automation and SVN related things.
> I can provide a UltraSparc for that. We can create a public repository
> with these packages for people who want to help.
> For me the main problem is the need of an unified build process.
Wouldn't the following be enough?
svn co package
svn-buildpackage
If #375973, and maybe #377880 would be fixed that could be done.
> Some packages that uses svn-buildpackage (like Boson) and don't have there
> tarball in tarballs/ because of there size.
> Therefore we need a script for that.
That should be placed, IMHO in svn/scripts/boson and that should be
ran via a prebuild action (see #375973). That would be generic enough
and elegant enough, IMO.
> So i suggest to have a scripts/pacakge.sh for such case that call
> svn-buildpackage if needed after.
or have #377880 fixed and realx.
> Something i want to see is to have EVERY package directly in
> trunk/packages/. No more trunk/package/package-data and
> trunk/package/package-data. This will reduct the complexity for scripting.
Yes, indeed, but as I said, I think scripting is not needed anyway,
*if* and only if we want to do buld related stuff.