Re: The future of gitweb (long term goals)

From: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date: Feb 22, 2011, 17:02 UTC
Message-ID: <AANLkTin9dWXkaxqLdiosx-=jA9gbEqoJ8aAFoZMU94ih@mail.gmail.com>
In-Reply-To: <201102142039.59416.jnareb@gmail.com>

On Mon, Feb 14, 2011 at 20:39, Jakub Narebski <jnareb@gmail.com> wrote:

Show 20 quoted lines

> This means that we are not able to use web (micro)framework, or use
> templating engine to create HTML instead of combination of CGI.pm
> methods and handcrafted HTML (worrying about proper escaping), or just
> use CGI::Cache or Plack::Middleware::Cache for adding output caching
> to gitweb.  Though if one wants web interface in Perl that uses web
> framework (and is supposedly backwards-compatible with gitweb URLs),
> there is always Gitalist which uses Catalyst web framework.
>
> On the other hand requiring non-core Perl modules means that gitweb
> installation would be harder.  We can work around this issue if there
> are a few small such modules (e.g. using Exception::Class or
> HTTP::Exception as base class for gitweb error handling) by putting
> them in 'inc/' and installing local version if they are not present,
> like Git.pm does with local Error.pm module.  But for microframework,
> or templating engine, or e.g. Plack (if we go the route to make gitweb
> PSGI application) this would be rather out of question.  Anyway, in
> any case gitweb would probably require more complicated build system
> than current one... but moving to e.g. ExtUtils::MakeMaker shouldn't
> be that hard (see how Git.pm does it, only we can require Perl 5.8.3
> which has new enough EU::MM that supports DESTDIR).

Why do you think that if we use larger modules these things would get harder?

There's already applications on the CPAN which can do "fat packing". I.e. you could use Plack, Catalyst, Template and whatever else but run some make target to pack gitweb and all its dependencies into a single file.

Obviously it would be really big, and probably slow unless you ran it as a fastcgi script. But that would be a tradeoff for making the source easier to maintain.

But packing things like these is not a technical challange at all, and probably way easier than reinventing the wheel each time you need some small thing that's not in core, but is in a popular & well tested CPAN module.