From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>,
Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] test-container: Add $complocaledir and mkdirp.
Date: Tue, 28 Apr 2020 15:59:32 -0400 [thread overview]
Message-ID: <78259811-aed5-b763-a73d-7a22489c4446@redhat.com> (raw)
In-Reply-To: <87blndfjvz.fsf@oldenburg2.str.redhat.com>
On 4/27/20 3:49 AM, Florian Weimer wrote:
> * Carlos O'Donell via Libc-alpha:
>
>> From 925c47b47d597663606486402c38e2e729ed663c Mon Sep 17 00:00:00 2001
>> From: Carlos O'Donell <carlos@redhat.com>
>> Date: Thu, 23 Jan 2020 09:45:00 -0500
>> Subject: [PATCH] test-container: Add $complocaledir and mkdirp.
>>
>> In order to test localedef in the test-container framework it
>> is necessary to add support for one new variable and one new
>> command. For localedef to install a compiled locale in the default
>> location the directory needs to be created
>> e.g. mkdir -p $complocaledir/dir. This command requires both the
>> new command 'mkdirp' e.g. mkdir -p, and the new variable
>> $complocaledir. The only way to avoid this would be to install
>> locales into the pristine container root, but that would slow down
>> container testing (currently only has builtin C/POSIX available).
>
> You could create the directory unconditionally, without installing any
> locales into it?
That's a very good point. I know of no reason we would want the directory
*not* to be present.
My argument is about saving time during testing and avoiding needing to
run 'make localedata/install-locales' and build all the SUPPORTED locales.
I'm going to adjust the patches and break them out like this:
- Create $(complocaledir) when making testroot.pristine
- Add new test.
- Fixup old test which uses xmkdirp to create $(complocaledir) since
it is no longer required.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2020-04-28 19:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 19:17 Carlos O'Donell
2020-04-27 7:49 ` Florian Weimer
2020-04-28 19:59 ` Carlos O'Donell [this message]
2020-04-28 22:03 ` DJ Delorie
2020-04-28 23:44 ` Carlos O'Donell
2020-04-29 0:12 ` DJ Delorie
2020-04-28 18:09 ` DJ Delorie
2020-04-29 15:55 ` [PATCH v2] test-container: Support $(complocaledir) " Carlos O'Donell
2020-04-29 17:57 ` DJ Delorie
2020-04-29 21:31 ` [PATCH v3] " Carlos O'Donell
2020-04-29 22:57 ` DJ Delorie
2020-04-30 20:29 ` Carlos O'Donell
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=78259811-aed5-b763-a73d-7a22489c4446@redhat.com \
--to=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).