Le Tue, 28 Jun 2005 11:27:05 -0400, Chris Gianelloni a écrit :
> Actually, that is the only current course of action that is acceptable.
Perfect ;-)
> The templates are documentation. They are all empty on purpose, as you
> are either supposed to fill them in yourself, after copying the template
> to a spec file for your own use, or you remove the option if you do not
> use it. The documentation above each option is the important part.
Yes, of course, but if I want YOUR specs (the one you used to build
livecd minimal), what have I to use ?
specs in livecd-ng OR options examples from templates doc ?
> Not really. If I get annoyed, I'll just quit answering and let other
> members of the catalyst-hate group answer... :P
;-)
the latest possible (google's translation)
> I need to make that more apparent.
I think so...
>> Ah, not portage_postdir anymore ?
>
> portage_confdir...
sorry.
>> And, If I want a USE is used by only one package (for exemple a plugin for
>> mozilla, but I don't want all packages with USE="mozilla") ?
>
> This would require portage_confdir.
Ok.
> We don't use portage_confdir when
> building releases, however. I also personally dislike it, as it removes
> the transparency of being able to give someone a spec file.
I think I can understand the difference now.
>> Another question, important even if I forgot it before, what is the best
>> way to modify some configuration files eg : /etc/fstab to mount nfs etc....
>> ?
>
> Use livecd/fsscript to add a shell script to be executed to perform any
> additional tasks. You can even use it for merging packages with crazy
> USE flags... *grin*
Ok, perfect.
Thank you for all.
I'll try to build now, so, I'll be back :-D
--
Christophe PEREZ
|
