<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.30.2">
</HEAD>
<BODY>
<BR>
I do all these by using spacewalk already on CentOS systems (<A HREF="http://www.google.co.uk/url?sa=t&source=web&cd=7&ved=0CEEQFjAG&url=https%3A%2F%2Ffedorahosted.org%2Fspacewalk%2F&ei=Ohx9TNjMLt6T4ga2_cn9BQ&usg=AFQjCNHnchovuxCJZ8NuT7GvNq1Uj4l3hA.">fedorahosted.org/spacewalk).</A><BR>
<BR>
Ege<BR>
<BR>
<BR>
On Mon, 2010-08-30 at 09:15 +0100, Aaron Trevena wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
On 30 August 2010 06:55, DL Neil <<A HREF="mailto:GLLUG@getaroundtoit.co.uk">GLLUG@getaroundtoit.co.uk</A>> wrote:
>> I'm working on a "smart mirror" catalyst web application and was
>> wondering how many people use their own repos, mirrors and mini-cpans
>> to get an idea of usage etc and if people would pay for somebody else
>> to provide something like that for them, yes it'll be all or mostly
>> open sourced, if it's successful I'd like to be able to provide some
>> commercial services to cover the project development costs and/or
>> subsidise my other open source coding.
>
> I suspect I'm not smart enough to understand what you mean by
> "catalyst", or for that matter "smart".
Catalyst would be <A HREF="http://www.catalystframework.org/">http://www.catalystframework.org/</A> a perl "MVC" framework.
"Smart" would be a nice web interface making it easy to categorise
packages into virtual repos for dev, staging, test, live, etc and pull
from multiple upstream repos, with the aim of providing a nice
dashboard showing which upstream packages are available, upstream
security fixes, and a nice audit trail.
> I maintain in-house repositories for CentOS rpms, just as others do for
> Debian et-al's apt (etc); with the idea that the WAN download happens
> once, but LAN distributions can initiate as many times as necessary (and
> in whatever form is appropriate) without bandwidth charge.
That seems pretty common. I thought the management of which packages
would be the main reason for people do it, but most responses have
been about mirroring for faster/cheaper download.
I'm not sure how much it would be possible to integrate into upstream
bug tracking, version control and puppet, etc
A.
--
Aaron J Trevena, BSc Hons
<A HREF="http://www.aarontrevena.co.uk">http://www.aarontrevena.co.uk</A>
LAMP System Integration, Development and Consulting
</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>