From: Trevor Woerner <twoerner@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 1/1] lib/bb/utils: add safeguard against recursively deleting things we shouldn't
Date: Mon, 20 Apr 2015 09:46:19 -0400 [thread overview]
Message-ID: <5535032B.4000007@gmail.com> (raw)
In-Reply-To: <54b162c649388c63015cdd0d69866d5604303b60.1429280244.git.paul.eggleton@linux.intel.com>
On 15-04-17 10:26 AM, Paul Eggleton wrote:
> Add some very basic safeguard against recursively deleting paths such
> as / and /home in the event of bugs or user mistakes.
>
I liked Nicolas Dechesne's idea of only allowing deletion in paths that
include TMPDIR or TOPDIR. Is there any reason bitbake would need to
delete (potentially dangerous) paths anywhere else?
With a list-based approach the list will keep growing indefinitely.
Inevitably an ex-Solaris person will come along (for example) and have
their /home directories in /export/home and need a patch for that, etc,
etc...
next prev parent reply other threads:[~2015-04-20 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 14:26 [PATCH 0/1] Add deletion safeguard Paul Eggleton
2015-04-17 14:26 ` [PATCH 1/1] lib/bb/utils: add safeguard against recursively deleting things we shouldn't Paul Eggleton
2015-04-20 13:46 ` Trevor Woerner [this message]
2015-04-20 13:59 ` Paul Eggleton
2015-04-20 22:04 ` Richard Purdie
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=5535032B.4000007@gmail.com \
--to=twoerner@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.