From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Is portage (/usr)/bin-merge safe?
Date: Sat, 1 Jun 2013 02:17:37 -0400 [thread overview]
Message-ID: <201306010217.38261.vapier@gentoo.org> (raw)
In-Reply-To: <pan$7796a$b69709b7$19290aaf$1cb9a749@cox.net>
[-- Attachment #1: Type: Text/Plain, Size: 300 bytes --]
On Saturday 01 June 2013 01:36:28 Duncan wrote:
> As in subject, is portage bin/usr-bin merge safe?
portage should be merge safe for all files. it specifically writes it to a temp
file and then does a rename so it's an atomic update. otherwise you'd get
things like ETXTBSY errors.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-06-01 6:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-01 5:36 [gentoo-portage-dev] Is portage (/usr)/bin-merge safe? Duncan
2013-06-01 5:49 ` Zac Medico
2017-12-07 8:37 ` [gentoo-portage-dev] " Duncan
2017-12-07 9:07 ` Zac Medico
2017-12-07 12:14 ` Duncan
2013-06-01 6:17 ` Mike Frysinger [this message]
2013-06-02 11:14 ` [gentoo-portage-dev] " vivo75
2013-06-02 11:54 ` [gentoo-portage-dev] " Duncan
2013-06-02 12:47 ` vivo75
2013-06-02 13:19 ` Duncan
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=201306010217.38261.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-portage-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