From: Chris S. <chr...@gm...> - 2007-10-09 13:27:57
|
I've got room to host those files on my Instalinux web hosting. I think my quota is around 250GB, and I'm using around 35GB... Chris On 10/9/07, Louis Bouchard <lou...@hp...> wrote: > Hi Bruno, > > Le mardi 09 octobre 2007 =E0 08:10 +0000, Cornec, Bruno (Linux Consultant= ) > a =E9crit : > > Hello, > > > > In order to help spread the adoption of LinuxCOE, I proposed to reuse > > the setp of scripts/tools I developped for the MondoRescue project. > > > > Looking at them, they were clearly too tightly integrated with mondo to > > make an easy reuse, so I decided to re-start from scratch and write a > > 3rd version of my packaging tools, this time unrelated to a specific pr= oject. > > > > This is called ProjectBuilder (aka pb). Cf: > > http://trac.project-builder.org > > > > The tool is written in perl, and provides the following functions: > > > > cms2build: Create tar files for the project under your CMS > > CMS supported are SVN and CVS > > > > build2pkg: Create packages for your running distribution > > > > cms2pkg: cms2build + build2pkg > > > > build2ssh: Send the tar files to a SSH host > > > > pkg2ssh: Send the packages built to a SSH host > > > > build2vm: Create packages in VMs, launching them if needed > > and send those packages to a SSH host once built > > VM type supported are QEMU > > > > cms2vm: cms2build + build2vm > > > > launchvm: Launch one virtual machine > > > > script2vm: Launch one virtual machine if needed > > and executes a script on it > > > > > > They are mostly all working for both mondo (SVN) and LinuxCOE (CVS). > > I've produced last week my first packages for Mandriva (my native > > distro) and I'm in the process of upgrading all my VMs (QEMU based) in > > order to be able to produce my next MondoRescue version (2.2.5) using > > that system (60% done). Once it's done, I'll also be able to generate > > packages for LinuxCOE for the same set of distro. All RPMs based distro > > are now working (fedora, rhel, mandriva, sles, suse), and I'm convertin= g the > > .deb based VMs. Gentoo, Slackware will follow. > > > > Once it's done, I'll be able to share all those VMs (as long as you hav= e > > the necessary place to host them, as they represent around 50 GB right > > now) so that everybody will be able to use the same mecanism to build > > it's own project. > > > > This is very good news to me ! This is indeed one of the issues in > developing the .spec files : coherent RPM production & testing. > > > Now specifically for LinuxCOE, I've worked on systemdesigner and > > systemdesigner-docs packages up to now. But in order to have a useful > > system, I'd need a package supporting one distribution. > > But (there is always a but ;-), packaging a set of binary files is > > really not appealing to me. > > > > Have someone already worked on a script that would allow to generate > > from a distro the files needed by LinuxCOE, without embedding them in a > > package ? (after all it's generated so shouldn't be part of neither the > > package, nor the CVS IMHO) ? > > > > Not to me & Brian either ! This is why we decided to remove the images > out of the RPM/DEBS. A separate tarball containing only the content of > the ./images directory will be made available separately, as well as a > script that will generate the images from a waystation. > > I don't now if BG has had time to make the necessary modifications to > the configure/make files required to avoid building the images. Once > it's done, I have the spec files ready to build the Overlay packages > _WITHOUT_ the binaries. > > Hope it helps, > > ...Louis > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Linuxcoe-devel mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxcoe-devel > > > |