Hi,

On 13.11.2017 23:56, Michael Tremer wrote:
> Hi,
> 
> On Sun, 2017-11-12 at 11:11 +0100, Matthias Fischer wrote:
>> Hi,
>> 
>> On 12.11.2017 01:34, Matthias Fischer wrote:
>> > Hi,
>> > 
>> > For details see:
>> > https://sourceforge.net/projects/squid-graph/
>> > ...
>> After looking at this, I thought it would be better and easier to
>> maintain this addon if I build and pack it like 'squid-accounting' or
>> 'wio' (e.g.).
> 
> Well, since there is an upstream project, I think it is probably best
> to use their tarball and have patches against the latest release.

Somehow I knew you would write that... ;-)
I thought about that, too.

> However, this is indeed quite old, so it might make sense to fork it
> and have an own git repository to work on it and release every once in
> a while. Like we do with guardian...
> 
> Maybe it makes sense to get in touch with the original maintainer and
> see where that goes. That depends on what changes you are going to
> make.

Hm. I have the feeling that this could be a timeconsuming procedure with
some up and downs and I would want to get this thing done somehow. So
prior to search for a - in the meantime no longer existent? - original
maintainer, I'd prefer to use the upstream package like in acient days
(IPCop) and apply a patch. I don't change anything in the original
working code, I just do some 'polishing'.

IPCop did it that way with some 'sed'-lines. There is only one file to
patch, everything else are added scripts from us for integration in
IPFire (controlling, polishing and localisation) and for Pakfire.

As a result we would have ONE file to download and a few files to
maintain which could be easily done through GIT.

What do you think?

Best,
Matthias