On Sun, Aug 2, 2009 at 1:32 PM, John Napiorkowski<jjn1...@yahoo.com> wrote: > > > > > ----- Original Message ---- >> From: Tomas Doran <bobtf...@bobtfish.net> >> To: The elegant MVC web framework <catalyst@lists.scsys.co.uk> >> Sent: Tuesday, July 28, 2009 8:28:08 PM >> Subject: Re: [Catalyst] RFC: no make install on catalyst apps >> >> >> On 28 Jul 2009, at 14:14, Marcus Ramberg wrote: >> >> > I see catalyst apps being complete CPAN packages as a real advantage. >> > Taking away the make install option seems very limiting >> >> +1 >> >> I would very much support moving to a 'real' sharedir for templates / config >> etc, rather than the current hacks (given appropriate back compat) however. >> >> Cheers >> t0m >> > > I am vaguely planning something roughly based on the XDG directory > specification: > > http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html > > for localizing configs and related. Something like this would make is much > easier to have multiply versions of the same catalyst application running. > Like, if I had MojoMojo installed and wanted to run two seperate wikis with > different configs. You can do that now but requires playing with %ENV and > copying some configs around. > > In my mind the way this would work is that you'd have the config and other > share data stuff as templates inside your dist, and than at install time we'd > copy to all the correct places. Then we'd merge configurations in the > following order. > > $cpan/config/myapp.conf > $home/.config/myapp.conf > /etc/myapp.conf > > Where $cpan is where cpan stuff is installed globally, $home is your home > directory. Maybe we could move around the order a bit, but this way we'd set > all the 'no moving parts here' config in the $cpan (stuff like when the app > was installed, some paths). Then whatever user started the app, we'd read > from her local configuration (we'd probably need some sort of 'first time' > script if it's not present, which would copy from a template and prompt for > required values) and last we'd merge in any globally set up stuff. > > Maybe with more people using local lib this is not as important, although I > see local lib most as a developer tool or as a workaround for people that are > on shared servers. > > That's just for config, but could work as well for search paths for templates
So config is supposed to move into a 'config' subdir (and later be merged with the configs in home and etc)? Am I reading that right? Maybe we could call it 'etc' instead of config? And now templates - can we also move them into a 'templates' subdir? -- Zbigniew Lukasiak http://brudnopis.blogspot.com/ http://perlalchemy.blogspot.com/ _______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
