shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-11-14 15:21:37 +03:00
Code
0254e9448f
systemd/src/shared/path-util.h

73 lines
2.9 KiB
C
Raw Normal View History

util: split-out path-util.[ch]
2012-05-07 23:36:12 +04:00
/*-*- Mode: C; c-basic-offset: 8; indent-tabs-mode: nil -*-*/
tests: add some silly tests for path-util.c
2013-03-29 06:03:53 +04:00
#pragma once
util: split-out path-util.[ch]
2012-05-07 23:36:12 +04:00
/***
This file is part of systemd.
Copyright 2010-2012 Lennart Poettering
systemd is free software; you can redistribute it and/or modify it
under the terms of the GNU Lesser General Public License as published by
the Free Software Foundation; either version 2.1 of the License, or
(at your option) any later version.
systemd is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public License
along with systemd; If not, see <http://www.gnu.org/licenses/>.
***/
Add __attribute__((const, pure, format)) in various places I'm assuming that it's fine if a _const_ or _pure_ function calls assert. It is assumed that the assert won't trigger, and even if it does, it can only trigger on the first call with a given set of parameters, and we don't care if the compiler moves the order of calls.
2013-05-03 06:51:50 +04:00
#include <stdbool.h>
util: split-out path-util.[ch]
2012-05-07 23:36:12 +04:00
Add __attribute__((const, pure, format)) in various places I'm assuming that it's fine if a _const_ or _pure_ function calls assert. It is assumed that the assert won't trigger, and even if it does, it can only trigger on the first call with a given set of parameters, and we don't care if the compiler moves the order of calls.
2013-05-03 06:51:50 +04:00
#include "macro.h"
udev: move udev_rules_check_timestamp to shared I want to use this from a bulitin in a subsequent patch.
2013-10-26 02:36:49 +04:00
#include "time-util.h"
Add __attribute__((const, pure, format)) in various places I'm assuming that it's fine if a _const_ or _pure_ function calls assert. It is assumed that the assert won't trigger, and even if it does, it can only trigger on the first call with a given set of parameters, and we don't care if the compiler moves the order of calls.
2013-05-03 06:51:50 +04:00
DEFAULT_PATH_SPLIT_USR macro
2013-12-21 03:35:38 +04:00
#define DEFAULT_PATH_NORMAL "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin"
#define DEFAULT_PATH_SPLIT_USR DEFAULT_PATH_NORMAL ":/sbin:/bin"
run: allow non-absolute paths as command
2013-09-08 15:51:39 +04:00
#ifdef HAVE_SPLIT_USR
DEFAULT_PATH_SPLIT_USR macro
2013-12-21 03:35:38 +04:00
# define DEFAULT_PATH DEFAULT_PATH_SPLIT_USR
run: allow non-absolute paths as command
2013-09-08 15:51:39 +04:00
#else
DEFAULT_PATH_SPLIT_USR macro
2013-12-21 03:35:38 +04:00
# define DEFAULT_PATH DEFAULT_PATH_NORMAL
run: allow non-absolute paths as command
2013-09-08 15:51:39 +04:00
#endif
Add __attribute__((const, pure, format)) in various places I'm assuming that it's fine if a _const_ or _pure_ function calls assert. It is assumed that the assert won't trigger, and even if it does, it can only trigger on the first call with a given set of parameters, and we don't care if the compiler moves the order of calls.
2013-05-03 06:51:50 +04:00
bool is_path(const char *p) _pure_;
char** path_split_and_make_absolute(const char *p);
util: split-out path-util.[ch]
2012-05-07 23:36:12 +04:00
int path_get_parent(const char *path, char **parent);
Add __attribute__((const, pure, format)) in various places I'm assuming that it's fine if a _const_ or _pure_ function calls assert. It is assumed that the assert won't trigger, and even if it does, it can only trigger on the first call with a given set of parameters, and we don't care if the compiler moves the order of calls.
2013-05-03 06:51:50 +04:00
bool path_is_absolute(const char *p) _pure_;
char* path_make_absolute(const char *p, const char *prefix);
char* path_make_absolute_cwd(const char *p);
path-util: add path_make_relative() In user_dirs() in path-lookup.c, I want to replace this: symlink("../../../.config/systemd/user", data_home); with symlink(config_home, data_home); to avoid hardcoding .config when XDG_CONFIG_HOME is set. The problem is that config_home is an absolute path, and it's better to make the symlink relative. path_make_relative() is an utility function that converts an absolute path into a relative one.
2014-05-03 12:52:12 +04:00
int path_make_relative(const char *from_dir, const char *to_path, char **_r);
Add __attribute__((const, pure, format)) in various places I'm assuming that it's fine if a _const_ or _pure_ function calls assert. It is assumed that the assert won't trigger, and even if it does, it can only trigger on the first call with a given set of parameters, and we don't care if the compiler moves the order of calls.
2013-05-03 06:51:50 +04:00
char* path_kill_slashes(char *path);
char* path_startswith(const char *path, const char *prefix) _pure_;
bool path_equal(const char *a, const char *b) _pure_;
Add utility function to append root to path
2014-07-26 22:47:31 +04:00
char* path_join(const char *root, const char *path, const char *rest);
Add __attribute__((const, pure, format)) in various places I'm assuming that it's fine if a _const_ or _pure_ function calls assert. It is assumed that the assert won't trigger, and even if it does, it can only trigger on the first call with a given set of parameters, and we don't care if the compiler moves the order of calls.
2013-05-03 06:51:50 +04:00
char** path_strv_make_absolute_cwd(char **l);
shared: rename path_strv_canonicalize_absolute functions Since 12ed81d9 path_strv_canonicalize_absolute leaves the search list relative to the given root directory instead of resolving paths to their true location as the name implies. To better reflect this behavior rename to the less strongly worded path_strv_resolve.
2014-06-20 06:07:02 +04:00
char** path_strv_resolve(char **l, const char *prefix);
char** path_strv_resolve_uniq(char **l, const char *prefix);
util: split-out path-util.[ch]
2012-05-07 23:36:12 +04:00
int path_is_mount_point(const char *path, bool allow_symlink);
int path_is_read_only_fs(const char *path);
path-util: unify code for detecting OS trees This also makes sure we always detect an OS tree the same way, by checking for /etc/os-release.
2013-04-16 07:47:04 +04:00
int path_is_os_tree(const char *path);
run: allow non-absolute paths as command
2013-09-08 15:51:39 +04:00
Do not check for existence of remote binaries systemd-run would fail when run with -M or -H and an absolute path, if this path did not exists locally. Allow it to continue, since we don't have a nice way of checking if the binary exists remotely. The case where -M or -H is used and a local path is unchanged, and we still iterate over $PATH to find the binary. We need to convert to an absolute path, and we don't have a nice mechanism to check remotely, so we assume that the binary will be located in the same place locally and remotely. http://lists.freedesktop.org/archives/systemd-devel/2014-November/025418.html
2014-11-23 02:00:07 +03:00
int find_binary(const char *name, bool local, char **filename);
util: add macro for iterating through all prefixes of a path Syntactic sugar in a macro PATH_FOREACH_PREFIX.
2013-09-25 22:58:23 +04:00
No need to canonicalize fixed paths
2014-01-09 02:41:41 +04:00
bool paths_check_timestamp(const char* const* paths, usec_t *paths_ts_usec, bool update);
udev: move udev_rules_check_timestamp to shared I want to use this from a bulitin in a subsequent patch.
2013-10-26 02:36:49 +04:00
fsck: Search for fsck.type in PATH Modifies find_binary() to accept NULL in the second argument. fsck.type lookup logic moved to new fsck_exists() function, with a test.
2014-04-13 00:07:45 +04:00
int fsck_exists(const char *fstype);
util: properly handle the root dir in PATH_FOREACH_PREFIX Also add PATH_FOREACH_PREFIX_MORE which includes the specified dir itself in the iteration
2013-09-26 21:58:33 +04:00
/* Iterates through the path prefixes of the specified path, going up
* the tree, to root. Also returns "" (and not "/"!) for the root
* directory. Excludes the specified directory itself */
util: add macro for iterating through all prefixes of a path Syntactic sugar in a macro PATH_FOREACH_PREFIX.
2013-09-25 22:58:23 +04:00
#define PATH_FOREACH_PREFIX(prefix, path) \
shared: path-util - try to make PATH_FORECH_PREFIX look less wrong We replace the idiom "X && !(*foo = 0)" with "X && ((*foo = 0), true)". This is not a functional change, but should hopefully make it less likely that people and static analyzers believe there is a typo here (i.e., to make it clear that the intention was not "X && *foo != 0"). Thanks to David Herrmann for the suggestion.
2014-09-25 18:12:41 +04:00
for (char *_slash = ({ path_kill_slashes(strcpy(prefix, path)); streq(prefix, "/") ? NULL : strrchr(prefix, '/'); }); _slash && ((*_slash = 0), true); _slash = strrchr((prefix), '/'))
util: properly handle the root dir in PATH_FOREACH_PREFIX Also add PATH_FOREACH_PREFIX_MORE which includes the specified dir itself in the iteration
2013-09-26 21:58:33 +04:00
/* Same as PATH_FOREACH_PREFIX but also includes the specified path itself */
#define PATH_FOREACH_PREFIX_MORE(prefix, path) \
shared: path-util - try to make PATH_FORECH_PREFIX look less wrong We replace the idiom "X && !(*foo = 0)" with "X && ((*foo = 0), true)". This is not a functional change, but should hopefully make it less likely that people and static analyzers believe there is a typo here (i.e., to make it clear that the intention was not "X && *foo != 0"). Thanks to David Herrmann for the suggestion.
2014-09-25 18:12:41 +04:00
for (char *_slash = ({ path_kill_slashes(strcpy(prefix, path)); if (streq(prefix, "/")) prefix[0] = 0; strrchr(prefix, 0); }); _slash && ((*_slash = 0), true); _slash = strrchr((prefix), '/'))
Copy Permalink