From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mutt: fix build with BR2_PACKAGE_SKELETON_NONE
Date: Sun, 6 Aug 2017 22:44:33 +0200 [thread overview]
Message-ID: <20170806204433.GC2921@scaer> (raw)
In-Reply-To: <23d9ad1d2c270c942d286f0fdf779dabfb876ffd.1502042905.git.baruch@tkos.co.il>
Baruch, All,
On 2017-08-06 21:08 +0300, Baruch Siach spake thusly:
> BR2_PACKAGE_SKELETON_NONE does not provide the /var subdirectory which break
> symlink creation in that directory. Ignore the symlink creation error. It is
> up to the user to provide a functional skeleton.
Note that this defconfig does not use a custom skeleton; it uses the
default skeleton. In this situation, the user is not providing the
skeleton, so he has no chance to "provide a functional skeleton."
Instead, we must ensure that our default skeleton for the "none" init
system is correct.
So, we have two options:
- provide /var in the skeleton-none
- have mutt do the mkdir as it needs it
My preference goes with the second solution, because it looks to me that
it is the best solution: mutt needs /var? Then it has to ensure that
/var exists before it uses it.
I do agreee however that one may consider that /var is a "magic"
directory, like /etc or /bin and /lib, and that it should always exist.
Nonetheless, I believe the second solution is still technically better,
because it does not make any assumption.
Care to respin by doing an mkdir, please?
Regards,
Yann E. MORIN.
> Fixes:
> http://autobuild.buildroot.net/results/32d/32dff0df759baf1120e4f11335e735eb0708b237/
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> package/mutt/mutt.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/mutt/mutt.mk b/package/mutt/mutt.mk
> index abd40e5dd612..447c336b4893 100644
> --- a/package/mutt/mutt.mk
> +++ b/package/mutt/mutt.mk
> @@ -66,7 +66,7 @@ MUTT_CONF_ENV += \
> MUTT_CONF_OPTS += --with-mailpath=/var/mail
>
> define MUTT_VAR_MAIL
> - ln -sf /tmp $(TARGET_DIR)/var/mail
> + -ln -sf /tmp $(TARGET_DIR)/var/mail
> endef
> MUTT_POST_INSTALL_TARGET_HOOKS += MUTT_VAR_MAIL
>
> --
> 2.13.2
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2017-08-06 20:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-06 18:08 [Buildroot] [PATCH] mutt: fix build with BR2_PACKAGE_SKELETON_NONE Baruch Siach
2017-08-06 20:44 ` Yann E. MORIN [this message]
2017-08-07 17:57 ` Baruch Siach
2017-08-08 16:07 ` Yann E. MORIN
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=20170806204433.GC2921@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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.