Include tools with MailScanner distro

[Ugo Bellavance]

Brendan Pirie wrote:
> Julian Field wrote:
>>
>>
>> Ugo Bellavance wrote:
>>> Richard Siddall wrote:
>>>> Ugo Bellavance wrote:
>>>>> Well, it would be good, but having a package, or, even better, a 
>>>>> repository, would be better.  The best would have tools distributed 
>>>>> with MailScanner, but this involves more (Julian doesn't want to 
>>>>> receive e-mails about a script that someone else wrote, extra work 
>>>>> for julian, etc).
>>>>>
>>>>
>>>> In one project I work on, parts of the wiki are generated from the 
>>>> source code.  Presumably you could go the other way around too. 
>>>> However, this is all extra work for somebody.
>>>
>>> It that is not too much work, the somebody could be me.
>>>
>>>> By "repository", are you talking about something like yum/apt, or 
>>>> CVS/SVN?
>>>
>>> If we generate a RPM, it may be easy to put it in a yum/apt 
>>> repository.    We could use CVS/SVN for source code, but I'm less 
>>> familiar with that.
>> I think a simple tarball would be more convenient for most people. An 
>> RPM is all very well for RedHat folks, but then you've got to 
>> distribute one RPM for RedHat, another for SuSE, an apt for Debian, a 
>> tarball for non-Linux, it all gets to be a complete nightmare and 
>> no-one will ever keep it up to date.
>>
>> Keep it simple. Just a directory of files would do just fine, so long 
>> as there is a manifest in each dir that tells you what file does what 
>> and where to put it. And a Readme that tells you how to use it.
>>
>> SVN is all very well for maintaining the code, but it won't be 
>> anyone's live development repository so there's not much point; again, 
>> it just makes it harder for people to contribute. You have to make it 
>> very easy for the authors as well as the users.
>>
>> My tuppence worth...
>>
>> Jules
>>
> Despite the fact that I use RHEL/CentOS, I'm inclined to agree.  This 
> should be made available in a non distro centric way.  Although, if one 
> wanted to include spec files in the tarballs that would facilitate the 
> use of rpmbuild, I wouldn't be inclined to object. ;)

Ok, makes sense.  What would be the best way to manage that.  I mean, I 
have some scripts, they work, but they might not be very robust.  Having 
a code repository could help so that others can improve my script and so 
on...

Ugo