Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Add crontab entries from package
Date: Thu, 26 Nov 2020 20:05:37 +0100	[thread overview]
Message-ID: <20201126200537.314f2576@gmx.net> (raw)
In-Reply-To: <92cb0f53-5289-afec-91e7-fc5e93bf29d2@klomp.eu>

Hello Sven,

On Thu, 26 Nov 2020 11:03:00 +0100, Sven Klomp <mail@klomp.eu> wrote:

> Hello,
>
> I want to add entries to /etc/crontabs/root.
> I know I can add abritary scripts to |BR2_ROOTFS_POST_BUILD_SCRIPT| to
> change files. However, as the crontab entry depends on the package, I
> want to change the file from within thepackage and not globally. How is
> this possible?
> The documentation of |BR2_ROOTFS_POST_BUILD_SCRIPT |makes me think there
> must be another solution:
> "You should, however, use this feature with care. Whenever you find that
> a certain package generates wrong or unneeded files, you should fix that
> package rather than work around it with some post-build cleanup scripts."

Maybe use a root filesystem overlay/BR2_ROOTFS_OVERLAY (see [1])...

Regards,
Peter

[1] https://buildroot.org/downloads/manual/manual.html#rootfs-custom


>
>
> Thanks
> Sven
> ||
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2020-11-26 19:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26 10:03 [Buildroot] Add crontab entries from package Sven Klomp
2020-11-26 19:05 ` Peter Seiderer [this message]
     [not found]   ` <b7ab5353-8504-055c-fcde-b1130dd53c43@klomp.eu>
     [not found]     ` <20201127235210.06a62c2a@gmx.net>
2020-11-27 22:53       ` Peter Seiderer

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=20201126200537.314f2576@gmx.net \
    --to=ps.report@gmx.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox