Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Add [user@host dir] back to skeleton /etc/profile
Date: Wed, 7 Oct 2015 21:58:02 +0100	[thread overview]
Message-ID: <5615875A.2010409@mind.be> (raw)
In-Reply-To: <561560C0.4030509@cmlab.biz>

On 07-10-15 19:13, David Van Arnem wrote:
> On 10/07/2015 10:56 AM, David Van Arnem wrote:
[snip]
>> I'd be happy to work on putting the changes back in
>> package/bash/bash_profile.  I've only used default
>> packages/configurations in Buildroot so I'm not very familiar with
>> modifying them, and I could use some guidance.  Should I place
>> bash_profile in package/bash and then have the bash package Makefile
>> copy it to system/skeleton/etc/profile?  Or is there another way I
>> should install it?
>>
>> David
>>
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
> 
> Upon more investigation, I have a (hopefully) better idea for how to accomplish
> this. Sticking with the suggestion in the commit message ("If the user has a
> specific needs, it needs to be added in /etc/profile.d/ by a post-build
> script."), I'm thinking I should create package/bash/bash_profile.sh, and in
> bash.mk set up a section to use $(INSTALL) to install it to
> $(TARGET_DIR)/etc/profile.d/bash_profile.sh. The skeleton /etc/profile sources
> any *.sh files in /etc/profile.d, so it should hopefully pick it up. Does this
> sound like a viable (and correct wrt best buildroot practices) approach?

 Sounds like a good idea to me!

 Regards,
 Arnout

> 
> Or, I'll just try it and see if it works :)


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2015-10-07 20:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06 22:59 [Buildroot] Add [user@host dir] back to skeleton /etc/profile David Van Arnem
2015-10-07  5:08 ` Baruch Siach
2015-10-07  8:22 ` Luca Ceresoli
2015-10-07 16:56   ` David Van Arnem
2015-10-07 18:13     ` David Van Arnem
2015-10-07 20:58       ` Arnout Vandecappelle [this message]
2015-10-08  7:51         ` Maxime Hadjinlian

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=5615875A.2010409@mind.be \
    --to=arnout@mind.be \
    --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