- Timestamp:
- 03/29/2006 07:59:36 PM (18 years ago)
- Branches:
- 1.0, 2.3, 2.3.x, 2.4, ablfs, ablfs-more, legacy, new_features, trunk
- Children:
- a0ed344
- Parents:
- 31d6944
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
TODO
r31d6944 rb287536 2 2 --------------- 3 3 4 ( Work for almost all this issues is in progress on the experimental branch)4 (The fixes for this issues are in the experimental branch) 5 5 6 6 CODE STYLE 7 7 ---------- 8 8 9 - To use the same coding style in all modules. The current used9 DONE - To use the same coding style in all modules. The current used 10 10 for HLFS module (colors, error-handling, etc) look a good starting 11 11 point for me, with two notes (to be discussed): … … 14 14 - Makefile code: to use eight-characters tabs. 15 15 16 - To set the "Date" and "Id" svn:keywords properties on all files16 DONE - To set the "Date" and "Id" svn:keywords properties on all files 17 17 setting the "Id" key on the header of each file and using the 18 18 "Date" key when needed (like in the -v output of jhalfs) … … 22 22 ------------- 23 23 24 - Make jhalfs a "master script" that will control and run each24 DONE - Make jhalfs a "master script" that will control and run each 25 25 book's module. When doing that reestructuration we coulud to change 26 26 the tool's name, if wanted. 27 27 28 - Common code for all modules should be placed in this master script.28 DONE - Common code for all modules should be placed in this master script. 29 29 30 - Common configuration options should be placed in a master configuration30 DONE - Common configuration options should be placed in a master configuration 31 31 file. 32 32 33 - The LFS, CLFS and HLFS modules should be exclusives. I.e., when33 DONE - The LFS, CLFS and HLFS modules should be exclusives. I.e., when 34 34 one is called the others must be ignored. 35 35 … … 44 44 ---------- 45 45 46 - To move the LFS module to their own subdir.46 DONE - To move the LFS module to their own subdir. 47 47 48 - Fix the unpack code to don't hang when both the bz2 and gz formats48 DONE - Fix the unpack code to don't hang when both the bz2 and gz formats 49 49 of the same package are founds in the sources dir. 50 50 … … 59 59 ----------- 60 60 61 - Start the module creation.61 DONE - Start the module creation. 62 62 63 63 … … 65 65 ----------- 66 66 67 - To review and fix, if needed, the bash and XSL code.67 DONE - To review and fix, if needed, the bash and XSL code. 68 68 69 - Be sure that the book's XML code is in a sane state.69 DONE - Be sure that the book's XML code is in a sane state. 70 70 71 - To do several build test for both Glibc and uClibc based systems.71 DONE - To do several build test for both Glibc and uClibc based systems. 72 72 73 73 … … 127 127 - To add support for ICA/farce? Can be done as a separate module? 128 128 129 - To add support for package management??? NO for this tool. Maybe in the130 under development new alfs tool.129 - To add support for package management??? NO by default, but patches 130 are acepted and will be added to the sources as external contributions. 131 131 132 132
Note:
See TracChangeset
for help on using the changeset viewer.