Re: Final toolchain dir

["Yann E. MORIN" <yann dot morin dot 1998 at anciens dot enib dot fr>]

Esben, All,

On Sunday 27 March 2011 14:30:33 Esben Haabendal wrote:
> "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> writes:
> > Yes, there is a way. See:
> >   Paths and misc options  --->
> >     [*] Render the toolchain read-only
> >
> > But, do you really, really need the toolchain to be writable? What for?
> 
> For the records, I really really need it to be writable.
> 
> Using ct-ng internally in OE-lite, I need the sysroot to be writable.
> 
> After completing the ct-ng built, the entire result is split up into a
> large number of packages (tar files), which is then later on use to
> (re)populate a complete staging dir when building other OE-lite
> recipes.  These staging dirs contain a carefuclly selected subset of the
> above mentioned ct-ng packages and whatever else is needed (typically
> other packages and build tools).  Rendering the ct-ng toolchain
> read-only would require OE-lite to go around changing back to sane
> permissions.  Also, target files are also directly used for
> building target images, and there I don't want to have the ct-ng built
> files to be forced to read-only.
> 
> So please, please, please (with sugar on top) let us keep the option to
> not have the toolchain rendered read-only :-)

Of course not! The default will stay 'y'. but the option will survive!
I do not intend to remove it at all! :-)

(hmmm! Sugar!)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  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.  |
'------------------------------^-------^------------------^--------------------'

--
For unsubscribe information see http://sourceware.org/lists.html#faq