Elfyn McBratney <[EMAIL PROTECTED]> tapota :
> (Please keep savannah-volunteers@ in the Cc - Thanks :-)
>
> Hello Savane devs, fellow hackers,
>
> The subject says it all: Adding site specific personalities to the back-end
> code (lib/... in CVS). My rationale is fairly cheeky: it makes maintaining
> Savannah specific changes in the sv_* scripts a doddle. ;-)
>
> But, it would also be a useful feature for any large site (like the ones in
> the Subject line) for installation specific code, IMO. It also has the
> benefit of good working example configurations for others to use. :-)
>
> Some specifics: To add a 'personality' you would use perl's Exporter module
> and export a tag (the site name.. that's the first one I've thought of -
> there's more, of course ;-), ala
>
> use Savannah 'Gna';
> use Savannah 'Subversions';
> use Savannah 'CERN';
>
> The plus side of this is that, you can use perl inheritance rules to make
> things even simpler, by having everything in the back-end as a default (a
> 'stub' if you want) function, that can be overridden by another module
> (personality, here).
>
> Does this sound OK? Maybe it would be better if I write a proper proposal
> with more information?
Sounds like a good starting point. :)
But in fact, I would tend to add real modules like
use Savannah::Gna
and these modules would contain stuf like
CvsMakeAreaAttic
("Attic" was a possible name for gna, until we made the final
decision).
And maybe it would be enough to add a
use Savannah::Gna
within savannah.conf.pl (I didnt tried).
--
Mathieu Roy
+---------------------------------------------------------------------+
| General Homepage: http://yeupou.coleumes.org/ |
| Computing Homepage: http://alberich.coleumes.org/ |
| Not a native english speaker: |
| http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english |
+---------------------------------------------------------------------+
_______________________________________________
Savane-dev mailing list
[EMAIL PROTECTED]
https://mail.gna.org/listinfo/savane-dev
