From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: FORGET IT. Re: [gentoo-catalyst] about the systemd-tmpfiles patches
Date: Tue, 18 Jan 2022 00:27:02 +0100 [thread overview]
Message-ID: <6185113.6fTUFtlzNn@pinacolada> (raw)
In-Reply-To: <3381292.n0HT0TaD9V@pinacolada>
[-- Attachment #1: Type: text/plain, Size: 1724 bytes --]
Forget it. This is a lot of pain for not much gain [*].
I've bumped build-docbook-catalog to version 2.2, which now uses
/etc/xml/.lock as lock directory (and creates it if needed).
[*]
On openrc profiles, running systemd-tmpfiles does not do anything since
no config files are installed. /run/lock is created somewhere inside
openrc, with different permissions compared to a systemd profile...
so we'd need to install a hand-crafted config...
That kind of gave me the last push towards a simpler solution.
Am Montag, 17. Januar 2022, 16:25:18 CET schrieb Andreas K. Huettel:
> on second thought, it probably makes sense to move the tmpfs mount and
> the systemd-tmpfiles call for stage1root *after* the installation of
> baselayout. started another test run...
>
> Am Montag, 17. Januar 2022, 15:51:22 CET schrieb Andreas K. Huettel:
> > 0) this is for bug 816303 and its fallout
> > https://bugs.gentoo.org/816303
> >
> > 1) for this to even have a chance of working, systemd-tmpfiles needs to be
> > in *stage1* (otherwise it can't be called at the start of the stage3
> > build).
> >
> > Since we can perfectly add whole systemd to packages.build, adding only
> > systemd-tmpfiles on openrc stages is no big deal (I checked, it works).
> >
> > 2) systemd-tmpfiles only does as much as its already present config says
> >
> > Which means we get an additional hook, but it's not doing too much yet.
> > I hope it's enough, so far I rebuilt stages 4 times with different package
> > sets and did not see any failures yet.
> >
> >
>
>
>
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
prev parent reply other threads:[~2022-01-17 23:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 14:51 [gentoo-catalyst] about the systemd-tmpfiles patches Andreas K. Huettel
2022-01-17 15:25 ` Andreas K. Huettel
2022-01-17 23:27 ` Andreas K. Huettel [this message]
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=6185113.6fTUFtlzNn@pinacolada \
--to=dilfridge@gentoo.org \
--cc=gentoo-catalyst@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