[gentoo-soc] Project GSE: Report for 19 of June to 23 of June: (ulfox)

[Christos Kotsis]

======================================================================================================================================================================================================================================================================
======================================================================================================================================================================================================================================================================

My plan for 19 of June was:
	-Create loop-hook-point functions to control the return value from the custom scripts and prompt for a SHELL if fail is returned
	-Write the controller's building script
	-Update the wiki page
	-Update the gse(1) and gse(2) man page.
	-Move everything inside to hook points. Giving the ability to run the gse process with completely custom scripts if someone wishes to.

Again I didn't finish controller's script. I had to implement a new function which will disable the interactive functions of the project, for the purpose of running the project full automated.
I couldn't finish the "automatic" function, since at a point I had to change many of the current functions to support the above, which broke the code at a point. I will try to finish this as my next objective.

My plan for 20 of June is:
	-Finish the automated process function
	-Create a new state function. It will save the configuration files, flags and arguments to a state-directory. From this someone can re-run the process again and again by referring to that state.
(I am including only those 2 objectives, since the last one will require much time, since it will take advantage of the above "automatic" function and use states at the same time)

======================================================================================================================================================================================================================================================================


My plan for 20 of June was:
	-Finish the automated process function
	-Create a new state function. It will save the configuration files, flags and arguments to a state-directory. From this someone can re-run the process again and again by referring to that state.
(I am including only those 2 objectives, since the last one will require much time, since it will take advantage of the above "automatic" function and use states at the same time)


I included 3 options for the state functions. Option to add,delete and initiate the states. I have not however finish the export function, which instead of saving the state, it reads it back and initiate the process.
The reason for not completing the export function was that I was trying to find a way to implement the above without changed all the current functions. This will be achieved with a new function that initiate a build only with that flag.

My plan for 21 of June is:
	-Finish the export state function
	-Update the menu entries
	-Update the man pages
	-Write a more general archive function instead of a simple tar cvjpf entry
	-Create a command line option for reviewing and editing the configuration files. Example gse --options_name:edit=hostname


======================================================================================================================================================================================================================================================================


My plan for 21 of June was:
	-Finish the export state function
	-Update the menu entries
	-Update the man pages
	-Write a more general archive function instead of a simple tar cvjpf entry
	-Create a command line option for reviewing and editing the configuration files. Example gse --options_name:edit=hostname


Dropped the command line option for reviewing and editing the configuration files. There are already tools to edit and view the config files.

My plan for 22 of June is:
	-Rewrite all functions to use if instead of &&, || pipes
	-Test the state combinations settings
	-Remove all unnecessary [[ ]], cat entries and use grep -q instead
	-Rewrite the clean function (update it with more entries, since the current one is failing during runtime sometimes).
	-Include an extra --keep-minimal function for the --build-minimal option. The current settings are included in the general clean function.


======================================================================================================================================================================================================================================================================

My plan for 22 of June was:
        -Rewrite all functions to use if instead of &&, || pipe
        -Test the state combinations setting 
        -Remove all unnecessary [[ ]], cat entries and use grep -q instead
	-Rewrite the clean function (update it with more entries, since the current one is failing during runtime sometimes).  
	-Include an extra --keep-minimal function for the 
--build-minimal option. The current settings are included in the genera

My plan for 22 of June is.
	-close the builder part (finish micro updates, and visuals)
	-start the controller part (rework the controller's scripts as dracut modules)
	-write the controller's build script (has not been finished, because it was trasfered for the next day in the past.
	-write extra controller examples in the man gse 5.

======================================================================================================================================================================================================================================================================

My plan for 23 of June was:
	-close the builder part (finish micro updates, and visuals
	-start the controller part (rework the controller's scripts as dracut modules)
	-write the controller's build script (has not been finished, because it was trasfered for the next day in the past.
	-write extra controller examples in the man gse 5.

 I implemented some custom dracut modules however I must enable the networking first in the initramfs to test them.

 My plan for 26 of June is:
	-Enable the networking in the controller.          
     
If I manage to enable networking, then:
	-Test the version check script
	-Write the fetch a new image module from the current scripts
	-Write the fetch config.d module from the current scripts

By current scripts I mean the scripts that I had written in the past, but not as dracut modules.
Those scripts as of now are parts in the main init file.

======================================================================================================================================================================================================================================================================
======================================================================================================================================================================================================================================================================