zeroday0619/MahiroOS-jhalfs
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Updated TODO

Browse source
This commit is contained in:
Manuel Canales Esparcia 2006-03-29 19:59:36 +00:00
parent 31d6944909
commit b287536032
1 changed files with 15 additions and 15 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

30
TODO
View file

@ -1,19 +1,19 @@
jhalfs TODO jhalfs TODO
--------------- ---------------
(Work for almost all this issues is in progress on the experimental branch) (The fixes for this issues are in the experimental branch)
CODE STYLE CODE STYLE
---------- ----------
- To use the same coding style in all modules. The current used DONE - To use the same coding style in all modules. The current used
for HLFS module (colors, error-handling, etc) look a good starting for HLFS module (colors, error-handling, etc) look a good starting
point for me, with two notes (to be discussed): point for me, with two notes (to be discussed):
- Bash code: to use two-spaces indentation (no tabs). - Bash code: to use two-spaces indentation (no tabs).
- Makefile code: to use eight-characters tabs. - Makefile code: to use eight-characters tabs.
- To set the "Date" and "Id" svn:keywords properties on all files DONE - To set the "Date" and "Id" svn:keywords properties on all files
setting the "Id" key on the header of each file and using the setting the "Id" key on the header of each file and using the
"Date" key when needed (like in the -v output of jhalfs) "Date" key when needed (like in the -v output of jhalfs)
@ -21,16 +21,16 @@ CODE STYLE
MASTER SCRIPT MASTER SCRIPT
------------- -------------
- Make jhalfs a "master script" that will control and run each DONE - Make jhalfs a "master script" that will control and run each
book's module. When doing that reestructuration we coulud to change book's module. When doing that reestructuration we coulud to change
the tool's name, if wanted. the tool's name, if wanted.
- Common code for all modules should be placed in this master script. DONE - Common code for all modules should be placed in this master script.
- Common configuration options should be placed in a master configuration DONE - Common configuration options should be placed in a master configuration
file. file.
- The LFS, CLFS and HLFS modules should be exclusives. I.e., when DONE - The LFS, CLFS and HLFS modules should be exclusives. I.e., when
one is called the others must be ignored. one is called the others must be ignored.
- The BLFS moudule should can be called in conjunction with any of - The BLFS moudule should can be called in conjunction with any of
@ -43,9 +43,9 @@ MASTER SCRIPT
LFS MODULE (some of this is applicable also to CLFS and HLFS modules) LFS MODULE (some of this is applicable also to CLFS and HLFS modules)
---------- ----------
- To move the LFS module to their own subdir. DONE - To move the LFS module to their own subdir.
- Fix the unpack code to don't hang when both the bz2 and gz formats DONE - Fix the unpack code to don't hang when both the bz2 and gz formats
of the same package are founds in the sources dir. of the same package are founds in the sources dir.
- To add a switch to build the BLFS module dependencies at the end of - To add a switch to build the BLFS module dependencies at the end of
@ -58,17 +58,17 @@ LFS MODULE (some of this is applicable also to CLFS and HLFS modules)
CLFS MODULE CLFS MODULE
----------- -----------
- Start the module creation. DONE - Start the module creation.
HLFS MODULE HLFS MODULE
----------- -----------
- To review and fix, if needed, the bash and XSL code. DONE - To review and fix, if needed, the bash and XSL code.
- Be sure that the book's XML code is in a sane state. DONE - Be sure that the book's XML code is in a sane state.
- To do several build test for both Glibc and uClibc based systems. DONE - To do several build test for both Glibc and uClibc based systems.
BLFS MODULE BLFS MODULE
@ -126,7 +126,7 @@ OTHERS
- To add support for ICA/farce? Can be done as a separate module? - To add support for ICA/farce? Can be done as a separate module?
- To add support for package management??? NO for this tool. Maybe in the - To add support for package management??? NO by default, but patches
under development new alfs tool. are acepted and will be added to the sources as external contributions.