El 2022-06-03 23:52, DustDFG escribió:
> On Fri, Jun 3, 2022 at 4:46 PM Matías Fonzo <selk@dragora.org> wrote:
>>
>> El 2022-06-03 04:47, DustDFG escribió:
>> > On Thu, Jun 2, 2022 at 6:49 PM Matías Fonzo <selk@dragora.org> wrote:
>> >>
>> >> El 2022-06-02 09:29, DustDFG escribió:
>> >> > Hello Matias!
>> >> >
>> >> > I apologize for coming back to this
>> >> >
>> >> > On Thu, Apr 28, 2022 at 7:00 PM Matias Fonzo <selk@dragora.org> wrote:
>> >> >>
>> >> >> El 2022-04-27 04:12, DustDFG escribió:
>> >> >> > Hi,
>> >> >> >
>> >> >> >> No, I was talking about to modify the output of packages by default
>> >> >> >> (from Qi), but first I want to check if we can just include the
>> >> >> >> packages
>> >> >> >> in a ISO handling the category name in the packages, for e.g: all
the
>> >> >> >> @core.tlz packages for the ISO (CD 1).
>> >> >> >
>> >> >> > I think that if we don't worry about size of this iso image, it
doesn't
>> >> >> > look like
>> >> >> > a problem because we can use 'find' utility. I still can't understand
>> >> >> > what
>> >> >> > you
>> >> >> > mean. What does modification of packages by default means?
>> >> >>
>> >> >> The size of the ISO matters, since we have to create the images for
>> >> >> several CDs, in 700mb maximum. To achieve this you have to adjust or
>> >> >> change the output of the packages for the files containing the build
>> >> >> orders. For example, the packages generated from 00-core.order would
>> >> >> be
>> >> >> installed to /var/cache/qi/packages/cd1/ with the rest continuing to
>> >> >> wrap their output for the next CD number. So from stage 2 you can
>> >> >> create
>> >> >> the images for the CDs. It also gives the possibility of doing what
>> >> >> you
>> >> >> suggested before, once the packages are generated, they will be
>> >> >> available in the packages/ directory, when chrooting in, Qi can be
>> >> >> used
>> >> >> to install directly, for example. the core from
>> >> >> var/cache/qi/packages/cd1.
>> >> >>
>> >> >> Apart from this, my proposal is to create a rootfs, which you unpack
>> >> >> directly, which is more direct and faster than having to install
>> >> >> packages one by one via Qi.
>> >> >>
>> >> >
>> >> > What do you think the rootfs must contain?
>> >>
>> >> The rootfs can contain whatever the final system produces, usually
>> >> everything (packed in a tar.gz).
>> >>
>> >>
>> >
>> > It will be a big file. Why not tarlz?
>>
>> Because tar/gzip is more widely supported, and some laptops
>> (Chromebooks, if I'm not mistaken) only support this format (to be
>> loaded in a SD card), I don't know if other formats are supported.
>>
>> > I also want to ask you about temporary system. Can we pack it like a
>> > cross-compiler?
>>
>> I don't recommend it, since they contain the hard-coded paths to
>> fulfill
>> its purpose, a prior step ensuring that the final system build will
>> not
>> be contaminated by host system stuff.
>>
>>
>
> Is it only tools directory?
Yes, exactly. This does not represent a running system (with a kernel
image, etc.) but it is about temporary tools to build the final
system.