From: "William Hubbs" <williamh@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/baselayout:master commit in: /
Date: Thu, 26 Jan 2023 00:08:37 +0000 (UTC) [thread overview]
Message-ID: <1674691518.cd2a6014247b4a3b69b780a331e4d5a5f280c2d8.williamh@gentoo> (raw)
commit: cd2a6014247b4a3b69b780a331e4d5a5f280c2d8
Author: William Hubbs <williamh <AT> gentoo <DOT> org>
AuthorDate: Thu Jan 26 00:05:18 2023 +0000
Commit: William Hubbs <williamh <AT> gentoo <DOT> org>
CommitDate: Thu Jan 26 00:05:18 2023 +0000
URL: https://gitweb.gentoo.org/proj/baselayout.git/commit/?id=cd2a6014
drop fhs compatibility symlinks from the makefile
This is necessary since we want baselayout to own these links.
To do that, we need to create them in the ebuild.
Bug: https://bugs.gentoo.org/648880
Signed-off-by: William Hubbs <williamh <AT> gentoo.org>
Makefile | 5 -----
1 file changed, 5 deletions(-)
diff --git a/Makefile b/Makefile
index 22e4a174..ecc7b107 100644
--- a/Makefile
+++ b/Makefile
@@ -66,15 +66,10 @@ layout:
for x in $(KEEP_DIRS) ; do \
$(INSTALL_DIR) $(DESTDIR)$$x ; \
done
- ln -snf /proc/self/mounts $(DESTDIR)/etc/mtab
- ln -snf /run $(DESTDIR)/var/run
- ln -snf /run/lock $(DESTDIR)/var/lock
# Special dirs
chmod 0700 $(DESTDIR)/root
chmod 1777 $(DESTDIR)/var/tmp
chmod 1777 $(DESTDIR)/tmp
- # FHS compatibility symlinks stuff
- ln -snf /var/tmp $(DESTDIR)/usr/tmp
layout-usrmerge: layout
rm -fr ${DESTDIR}/bin
next reply other threads:[~2023-01-26 0:08 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 0:08 William Hubbs [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-12 1:39 [gentoo-commits] proj/baselayout:master commit in: / Mike Gilbert
2023-07-09 1:24 Mike Gilbert
2023-07-09 1:24 Mike Gilbert
2023-07-09 1:17 Mike Gilbert
2023-07-09 1:17 Mike Gilbert
2023-01-28 2:08 Mike Gilbert
2023-01-28 2:08 Mike Gilbert
2023-01-28 0:33 Mike Gilbert
2023-01-27 18:15 William Hubbs
2023-01-27 18:15 William Hubbs
2023-01-27 18:12 William Hubbs
2023-01-27 17:20 William Hubbs
2023-01-27 17:20 William Hubbs
2023-01-26 3:48 William Hubbs
2023-01-25 21:23 William Hubbs
2022-09-18 21:44 William Hubbs
2022-09-18 4:28 William Hubbs
2022-09-18 3:22 Mike Gilbert
2022-09-18 3:03 Mike Gilbert
2021-09-27 21:48 William Hubbs
2021-09-27 21:44 William Hubbs
2021-09-27 21:24 William Hubbs
2021-09-27 20:56 William Hubbs
2021-09-27 17:46 William Hubbs
2021-09-24 19:56 William Hubbs
2021-05-11 15:48 William Hubbs
2020-02-10 4:21 William Hubbs
2020-02-10 4:21 William Hubbs
2018-05-28 19:31 William Hubbs
2018-05-28 19:31 William Hubbs
2018-05-26 20:17 William Hubbs
2018-05-26 20:17 William Hubbs
2018-05-23 21:50 William Hubbs
2018-02-22 17:54 William Hubbs
2018-02-07 19:11 William Hubbs
2018-02-06 22:54 William Hubbs
2017-11-17 22:04 William Hubbs
2017-10-03 22:02 William Hubbs
2017-08-21 19:45 William Hubbs
2017-06-09 18:38 William Hubbs
2017-06-09 18:38 William Hubbs
2017-06-08 17:35 William Hubbs
2016-09-01 20:56 William Hubbs
2016-09-01 20:56 William Hubbs
2014-08-13 18:08 William Hubbs
2014-08-06 19:49 William Hubbs
2014-08-06 15:07 William Hubbs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1674691518.cd2a6014247b4a3b69b780a331e4d5a5f280c2d8.williamh@gentoo \
--to=williamh@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox