Re: [dev] lock (1) - where does it go?

From: Calvin Morrison <mutantturkey_AT_gmail.com>
Date: Tue, 12 Jan 2016 09:35:59 -0500

sorry to revive an old topic -

I'd like to have this in with other utils, because i find it useful in
my day to day work. I do not care about the licensing, feel free to
use whatever license is appropriate.MIT/X I think is what is used
around here.

 Would someone be willing to commit this into u/sbase for me?

Calvin

On 22 April 2014 at 17:53, sin <sin_AT_2f30.org> wrote:
> On Tue, Apr 22, 2014 at 05:34:47PM -0400, Calvin Morrison wrote:
>> On 22 April 2014 17:24, sin <sin_AT_2f30.org> wrote:
>> > On Tue, Apr 22, 2014 at 05:20:29PM -0400, Calvin Morrison wrote:
>> >> > How are you getting on with this? I am planning to do a bit more polishing
>> >> > to ubase + add 1-2 tools and then make an initial v0.1 release. Would
>> >>
>> >> wouldn't this fit better in sbase?
>> >
>> > depends... a naive implementation can be done portably and fit in sbase.
>> > if we put it in ubase, I suspect we'll fix it to work with inotify instead.
>> >
>>
>> might as well use inotify tools then
>>
>> inotifywait -e delete lock_dir
>
> the point is to have something light and self-contained.
>
> you might as well use gnu coreutils then.
>
Received on Tue Jan 12 2016 - 15:35:59 CET