On 24/02/14 01:19 AM, Daniel Baumann wrote:
> On 02/23/2014 11:43 PM, Daniel Dickinson wrote:
>> Currently each live-image is a separate entity
> 
> that's the general principle, a deliberate design decision we will, in
> general, not change.
> 
>> it is difficult, especially for elements like bootloaders and chroot 
>> includes, to maintain a set of common elements
>> from which you pick what applies to a given image (e.g. with symlinks) along 
>> with
>> it's unique elements.
> 
> for bootloader configuration, you can create a syslinux-theme-* debian
> package.

Erm, I seem to have missed that.  Is there a pointer to how that would
be done?

> for chroot includes, you can create a debian package as well.
> 
>> for binary hooks can work around this
> 
> right.
> 
>> adding a package would achieve this for chroot, creating a package is
>> a lot of work for the payoff
> 
> live-build is built primeraly for people who know debian packaging in
> order to get proper results, but we do provide fallbacks for people who
> don't (includes and hooks); after all, debian-live is for debian, not
> for slackware or lfs, or...

I guess I'm approaching it from a different perspective.  I'm not a
debian developer and rarely deal with package but frequently deal with
system administration and do coding all the time, so I was looking to
debian-live for an easy way to create a rescue cd with the packages I
wanted on it rather than in order to create a full-blown live distro.

>> I don't expect this will be worked on soon, but I make a note in case I or 
>> someone
>> else gets the time to do something about it.
> 
> do you have *concrete* suggestion? if not, i'm inclinded to close the
> bug because:
> 
>   * the target audience is debian packaging aware people
>   * we provide a fallback you can do everything with (hacky, but
>     possible)
>   * you can't have everything at the same time when it's
>     mutually exclusive (dereference symlinks or not)

I realize the symlink option won't work.  The only thing I really need
is a hook that runs before chroot is turned into an image that runs
outside the chroot.  That why I can get what I want from elsewhere and
stick in the chroot dir.

The bootloader thing is not such a big deal but being able to add to /
modify the chroot before it's squashed (or whatever, depending on
config) would be really, really useful.

Regards,

Daniel


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to