Jean McCormack wrote:
> Moinak Ghosh wrote:
>   
>> Karen Tung wrote:
>>   
>> [...]
>> So, my questions is: do you know exactly which GNOME package is required to
>> setup whatever it is necessary for the desktop to start?
>>
>> In the Live Media and the Slim Prototype code, the postrun stuff is run in
>> the proto area.  Then, the microroot is setup with the list of files in
>> the "mkbootcd.files.minimal".  I examined the mkbootcd.files.minimal file
>> carefully, and I don't see any obvious GNOME related stuff get copied over
>> to the microroot.  Does that mean the postrun for GNOME does not have to
>> happen in the microroot?  Perhaps if somebody can explain exactly how
>> the postrun stuff setup the GNOME desktop in the Live Media case, what kind
>> of GNOME desktop startup setup needs to be present in the microroot, 
>> then, we will
>> be able to better debug this problem with getting GNOME to start with
>> the Distro Constructor code.
>>   
>>     
>>     
>> [...]
>> All we need to build the microroot is a list of files. Given a list of 
>> packages that
>> should go into the microroot it should be possible to extract the list 
>> of files and
>> cpio them from the proto area rather than doing the pkgadds, 
>> postinstalls and all
>> the corresponding bloat. So we avoid the file list and avoid problems 
>> associated
>> with pkgadds.
>>   
>>     
> Moinak,
>
> This sounds like you're talking about "marking" files within a package. 
> So if you specified I want package X then this special package add
> (or whatever) would look within package X to see which files are marked 
> for the miniroot and only copy those.  These would be copied
> from the proto area and not the package repository. Is that because some 
> of the files in the proto area have been modified? Or just because they 
> are easily accessible in the proto area?
>   

   The marking will be a feature of the new packaging system.
   But for now I was indicating to copy all the files in the
   microroot package list. Actually do a cpio as opposed to a
   package install.

   It will avoid all the problems mentioned above and the postrun
   problem that Karen is facing. No package installation/configuration
   should happen in the miniroot. Everything should happen in the
   proto only once. The proto area is actually an installed and
   configured alternate root and that is the exact environment that
   the LiveCD should expose.

Regards,
Moinak.

> Jean
>   
>> Regards,
>> Moinak.
>>
>>   
>>     
>>> Thanks,
>>>
>>> --Karen
>>> _______________________________________________
>>> caiman-discuss mailing list
>>> caiman-discuss at opensolaris.org
>>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
>>>   
>>>     
>>>       
>> _______________________________________________
>> caiman-discuss mailing list
>> caiman-discuss at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
>>   
>>     
>
> _______________________________________________
> caiman-discuss mailing list
> caiman-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
>   


Reply via email to