Opened 11 years ago
Closed 9 years ago
#924 closed task (wontfix)
Remove the need / desire to make a 'clfs' user
| Reported by: | Andrew Bradford | Owned by: | Andrew Bradford |
|---|---|---|---|
| Priority: | minor | Milestone: | CLFS Embedded 1.0.0 |
| Component: | BOOK | Version: | CLFS Embedded GIT |
| Keywords: | Cc: |
Description
We should be able to modify the user's path such that the cross-tools get used when they should and the host's tools get used when they should. Other build tools like yocto/oe and buildroot do this without issue.
Removing the need to create a new user should make scripting a build less painful.
Change History (2)
comment:1 by , 11 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 9 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
OE actually creates an entirely new system, kind of like the cross-tools in the main book, but even more extreme, and then throws away the user's environment to make a new one. If you want any of your env settings to carry over into this new env, you have to set which ones you want via BB_ENV_EXTRAWHITE or similar mechanisms.
So trying to not have a separate user is likely going to be much much more difficult. Since we're manually making the build (unlike OE), just setting up a user who's configured to build correctly is probably the easiest way to do things.