Hello, It would be great having a system like this! I vote on it!
Luis Otavio de Colla Furquim On Sep 14, 9:27 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Hello, > > I have a suggestion that someone who has not got a 20% time project > yet could look into: > > It is making a frontend for the various distribution system used by > *NIX systems, and maybe even windows installer. > The basic idea would be that you can specify a location in your > repository where you keep makefiles, binaries,etc (also the > directories and settings files for DPKG et al). > > The system would then, when you specify it, either via web interface, > or by tagging in SVN, or even in a fixed time interval take this > information and convert it into various repository files and > directories. > > For example it takes the DPKG directories and your binaries and builds > a .deb file from it, which is automatically copied to a debian > repository. > Gentoo ports are packed, and moved to the repository as well. > Same for other port based systems. > .RPM files can also be put together. > .MSI files can also be created... > > etc... > > This system makes life for package releasers way easier. You just > commit your binaries to SVN ( i know that is in general not good, but > for stable binaries it helps here) press the GO button on the webpage > and your release appears in Debian,Gentoo,FreeBSD and the Windows > users can get the latest .MSI as well... > THe obvious completion of this would be a build farm that does nightly > GCC builds with various options and automatically packages your > files. > > I will try to make things clearer with an example. > > /svn/ - your svn repo > /svn/trunk/src - your sources in the trunk > /svn/trunk/ports/FreeBSD/Makefile - your FreeBSD Ports makefile > /svn/trunk/ports/Gentoo/Makefile - your Portage makefile > /svn/trunk/CMakeLists.txt - your CMAKE stuff, if you use it > /svn/trunk/configure - your Automake file, if you use it > /svn/trunk/Makefile - your Makefile, maybe also an example > output from automake or CMAKE > /svn/trunk/project.sln - Your microsoft stuff, if you use it > /svn/trunk/bin/linux/proj - Your Project Linux binaries > /svn/trunk/bin/win32/proj.exe - Your Project Windows binaries > /svn/trunk/bin/ - Other stuff > /svn/trunk/ports/DEBIAN - your .DPKG Input. > > When the next release shall be made the system takes the entire > repository minus the binaries and tar.bz2 it. > Now, if it is possible and there is a build farm, the build farm > builds the project for various platforms and automatically commits the > binaries to SVN. > It also uses the debian DPKG utilities to build packets from the > binaries in SVN, the Gentoo utilities to fix up a Gentoo emake, the > FBSD utilities to make a FreeBSD port, and one of the various > free .MSI utilities to make a Windows Installer file. > Then these files are (a) automatically uploaded to the downloads > section, and (b) the ports,.debs,.rpms, etc are copied to a special > download service with a URL like: > Debian repositoryhttp://project.googlecode.com/r/debian/Main > Gentooo http://project.googlecode.com/r/portage/ > FBSD http://project.googlecode.com/r/fbsd-port/ > > etc. so that the various utilities ( apt-get, emerge,pkg_add) can be > configured to find them. This would also allow the official > repositories ( Portage, Ports tree) to mirror and link to these URLs. > > This would help Google Code become even better for BIG open source > projects and these that want to become big. > > Nice Sunday, > Julian Bangert --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hosting at Google Code" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en -~----------~----~----~----~------~----~------~--~---
