[Slackbuilds-users] murmur SlackBuild

[Ben Mendis]

I concur, FWIW.

I am the same way, I use the client on a lot of systems but only run the
server on a headless server. I feel like it's natural to split them into
two packages even though they share the same source package.

I also agree that 'murmur' makes more sense than 'mumble-server'.


On Sat, Feb 25, 2012 at 1:54 AM, King Beowulf <kingbeowulf at gmail.com> wrote:

> On Fri, Feb 24, 2012 at 9:51 PM, James Geboski <jgeboski at gmail.com> wrote:
>
>> Hello,
>>
>> No worries about the delay.  I personally, find it more useful to have
>> them split into two packages.  Reason being, I do not have any of the
>> X libraries on the servers I am running murmur on.  And on the client end,
>> you really don't need murmur.  If anyone has any objections to this, please
>> inform me.
>>
>> Also, I'd find it "cleaner" to have /var/{lib,log,run}/mumble-server
>> renamed to /var/{lib,log,run}/murmur.  This way it matches the naming of
>> rc.murmur and murmurd.  However, people would not really be able upgrade
>> the package if this was implemented.  Would this be a forbidden to do in
>> the SlackBuild?
>>
>> James
>>
>>
> I agree on keeping the 2 as separate packages. I'm running murmur-1.2.3 on
> a headless box, and mumble-1.2.3 on the GUI clients.  2 packages keep it
> cleaner and simpler.
>
> As for '/var/{lib,log,run}/murmur' I can accept the rename.  A simple
> warning statement about doing a clean install in the readme should be
> sufficient. After all, we all read the readmes, right?
>
> -Ed
>
> --
> You! What PLANET is this!
>     -- McCoy, "The City on the Edge of Forever", stardate 3134.0
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20120225/a6f7982a/attachment.html>