> Hi,
>
> Do we need the extra command line options? I'm thinking about a hook dir where
It's all down to how you'd like this to behave, we can do that instead. I think the discussions on irc kept mentioning command line options which is why I did that. Any other opinions about cli options vs a hook dir?
> you drop your hooks, in the same way it's done on live-build [1] or
> pbuilder[2]. A prefix will determine at which stage the scripts will be used.
> Until the proper solution is implemented, you can hardcode the scripts name.
>
> [1] /usr/share/live/build/examples/hooks
> [2] /usr/share/doc/pbuilder/examples
>
> > 2. Would be useful if we could also copy both scripts at the rootfs
> > 3. Would also be useful if we could stamp that the image was customized by a
> script
>
> for both, I'll leave these outside of l-m-c. It's up to the developer and
> could be done through the hooks.
I think it can be settled by sorting out if this always will be needed or if there may be cases where the hook author would want no trace of the hooks on the target system. If we feel that we need this for helping people with messed up images we need to do it in l-m-c. If it's up to the developer, I'm happy to leave this bit out.
> Hi,
>
> Do we need the extra command line options? I'm thinking about a hook dir where
It's all down to how you'd like this to behave, we can do that instead. I think the discussions on irc kept mentioning command line options which is why I did that. Any other opinions about cli options vs a hook dir?
> you drop your hooks, in the same way it's done on live-build [1] or live/build/ examples/ hooks doc/pbuilder/ examples
> pbuilder[2]. A prefix will determine at which stage the scripts will be used.
> Until the proper solution is implemented, you can hardcode the scripts name.
>
> [1] /usr/share/
> [2] /usr/share/
>
> > 2. Would be useful if we could also copy both scripts at the rootfs
> > 3. Would also be useful if we could stamp that the image was customized by a
> script
>
> for both, I'll leave these outside of l-m-c. It's up to the developer and
> could be done through the hooks.
I think it can be settled by sorting out if this always will be needed or if there may be cases where the hook author would want no trace of the hooks on the target system. If we feel that we need this for helping people with messed up images we need to do it in l-m-c. If it's up to the developer, I'm happy to leave this bit out.