Hash :
5345b4c7
        
        Author :
  
        
        Date :
2021-07-06T07:39:36
        
      
allow lockfiles to be used in cases where we have a dir_fd and a relative path
/*
 * Copyright (c) 2019 Stefan Sperling <stsp@openbsd.org>
 *
 * Permission to use, copy, modify, and distribute this software for any
 * purpose with or without fee is hereby granted, provided that the above
 * copyright notice and this permission notice appear in all copies.
 *
 * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
 * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
 * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
 * ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
 * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
 * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 */
/*
 * Git-compatible lock file implementation. Lock files are used to
 * ensure exclusive access when files in a GIt repository are modified. 
 */
#define GOT_LOCKFILE_SUFFIX ".lock"
struct got_lockfile {
	char *path;
	char *locked_path;
	int fd;
};
const struct got_error *got_lockfile_lock(struct got_lockfile **,
    const char *, int);
const struct got_error *got_lockfile_unlock(struct got_lockfile *, int);