Re: [Slackbuilds-users] haskell-platform SlackBuild

2012-07-11 Thread Christoph Willing
On 12/07/2012, at 4:17 AM, Glenn Becker wrote: Hi all - I emailed the maintainer for the 13.1 SlackBuild of haskell- platform to ask whether he had any plans to update it for 13.37. He told me that he did not, and transferred SlackBuild maintenance responsibility to me. I don't yet hav

Re: [Slackbuilds-users] recode.SlackBuild

2012-07-11 Thread JK Wood
On Jul 11, 2012 1:11 PM, "Chris Abela" wrote: > > I was informed that the recode source link is dead. The source code is however available from a git repositoryhttps://github.com/pinard/recode > As I am not using recode anymore, I am offering the maintenance of the SlackBuild to anyone willing to

Re: [Slackbuilds-users] recode.SlackBuild

2012-07-11 Thread Klaatu
> I was informed that the recode source link is dead. The source code is > however available from a git repositoryhttps://github.com/pinard/recode As > I am not using recode anymore, I am offering the maintenance of the > SlackBuild to anyone willing to take up the job. > > Also, any offers to hos

Re: [Slackbuilds-users] haskell-platform SlackBuild

2012-07-11 Thread Glenn Becker
Hi all - I emailed the maintainer for the 13.1 SlackBuild of haskell-platform to ask whether he had any plans to update it for 13.37. He told me that he did not, and transferred SlackBuild maintenance responsibility to me. I don't yet have an accurate idea of how much work this might require

Re: [Slackbuilds-users] requirements in README files

2012-07-11 Thread Chris Abela
Normally I avoid charged and lengthy discussions but as the opinion of other maintainers was solicited in this correspondence, I thought I'd let you know my modest opinion as briefly as possible: Facilitating dependency queuing for possible optional parsing tools is a logical evolution of the

[Slackbuilds-users] recode.SlackBuild

2012-07-11 Thread Chris Abela
I was informed that the recode source link is dead. The source code is however available from a git repositoryhttps://github.com/pinard/recode As I am not using recode anymore, I am offering the maintenance of the SlackBuild to anyone willing to take up the job. Also, any offers to host the sou

Re: [Slackbuilds-users] requirements in README files

2012-07-11 Thread mr.chew.b...@gmail.com
I say leave it as is. Although I like the idea of dependency checks it scares me if there is an either or when you have neither installed. Sent via my mobile handheld communications device - Reply message - From: "Ben Mendis" To: "SlackBuilds.org Users List" Subject: [Slackbuilds-us

Re: [Slackbuilds-users] requirements in README files

2012-07-11 Thread J
Another thing which has been mentioned a few times, and which I have considered off and on myself, is a fork of the repo. There are several reasons I have not pursued this idea; it constitutes an amount of work which would keep me busy doing that for an unrealistic amount of time, or it req

Re: [Slackbuilds-users] requirements in README files

2012-07-11 Thread J
Quoting Christoph Willing : On 11/07/2012, at 2:01 PM, J wrote: [snip] 1. how does such a recommendation get communicated to slackbuild maintainers? admins out there, would you be willing to publish such a recommendation on slackbuilds.org? after all, if it weren't stated there, it wouldn