CVS: lunar-doc/History TODO.20030720,NONE,1.1

[elaine at lunar-linux.org]

Update of /var/cvs/lunar/lunar-doc/History
In directory dbguin.lunar-linux.org:/home/elaine/lpcvs/lunar-doc/History

Added Files:
	TODO.20030720 
Log Message:
first add


--- NEW FILE: TODO.20030720 ---
start putting ideas todo on the future in here!

1) 
ADDED BY nestu
TOPIC: Tarballs size
Add an option to show the size of a module's tarball, This can be done 
via lvu for example (e.g. lvu size <module>) and at "lin" time to know how much 
is doing to be DLed. This way it can be known previously if the download is 
worth it (time speaking for example) or if there is a better alternative 
(another module that can provide the same functionality with less dependencies). 
It would require resolving dependencies for all modules before any action is 
taken, in the case of lin. The module size could be useful for a lvu tree, a lvu 
depends, if wanted (secondary to lin's use). As pointed out on IRC, this could 
be achieved by an extra field in DETAILS, for example, or in moonbase, to keep 
things centralised.
COMMENTS:  
start putting ideas todo on the future in here!

Modified 200307201954
start putting ideas todo on the future in here!

1) 
ADDED BY nestu
TOPIC: Tarballs size
Add an option to show the size of a module's tarball, This can be done 
via lvu for example (e.g. lvu size <module>) and at "lin" time to know how much 
is doing to be DLed. This way it can be known previously if the download is 
worth it (time speaking for example) or if there is a better alternative 
(another module that can provide the same functionality with less dependencies). 
It would require resolving dependencies for all modules before any action is 
taken, in the case of lin. The module size could be useful for a lvu tree, a lvu 
depends, if wanted (secondary to lin's use). As pointed out on IRC, this could 
be achieved by an extra field in DETAILS, for example, or in moonbase, to keep 
things centralised.
Modified 200307201956
start putting ideas todo on the future in here!

1) 
ADDED BY nestu
TOPIC: Tarballs size
Add an option to show the size of a module's tarball, This can be done 
via lvu for example (e.g. lvu size <module>) and at "lin" time to know how much 
is doing to be DLed. This way it can be known previously if the download is 
worth it (time speaking for example) or if there is a better alternative 
(another module that can provide the same functionality with less dependencies). 
It would require resolving dependencies for all modules before any action is 
taken, in the case of lin. The module size could be useful for a lvu tree, a lvu 
depends, if wanted (secondary to lin's use). As pointed out on IRC, this could 
be achieved by an extra field in DETAILS, for example, or in moonbase, to keep 
things centralised.
elaine/TODO:item: Start own TODO
elaine/TODO:item: Core documents, functions, subroutines, module design
elaine/TODO:item: kernel code hash generation tool
elaine/TODO:item: Website re-design  
elaine/TODO:item: Selinux module/policy & metadata tools/config
elaine/TODO:item: NPTL module post-crash xxx
elaine/TODO:item: coalesce individual TODO's into master && perhaps add to private web
evildrew/TODO:item: 1. (Priority) Installation manual -- Handy guide to get people through the install and up and running.
evildrew/TODO:item: 2. Handy stuff on the command line -- Unique commands to lunar and how to use them to your advantage.
evildrew/TODO:item: 3. Core documentation -- The more serious version of #2.
nestu/TODO:item: 1) Tarball size in moonbase/lunar
sofar/TODO:item: add cpan:// urls and see if it can be made working with a default_cpan_build or something like that
sofar/TODO:item: add a uniform verification scheme that allows us to use one scheme to verify the valitidy of sourcefiles, possible syntax would be a DETAILS entry (SOURCE_VFY[0]=MD5:1a9e1f6c2c4b5a1d2827312) (SOURCE_VFY[1]=GPG:url-to-asc-file)
Modified 200307201959
elaine/TODO:item: Start own TODO
elaine/TODO:item: Core documents, functions, subroutines, module design
elaine/TODO:item: kernel code hash generation tool
elaine/TODO:item: Website re-design  
elaine/TODO:item: Selinux module/policy & metadata tools/config
elaine/TODO:item: NPTL module post-crash xxx
elaine/TODO:item: coalesce individual TODO's into master && perhaps add to private web
evildrew/TODO:item: 1. (Priority) Installation manual -- Handy guide to get people through the install and up and running.
evildrew/TODO:item: 2. Handy stuff on the command line -- Unique commands to lunar and how to use them to your advantage.
evildrew/TODO:item: 3. Core documentation -- The more serious version of #2.
nestu/TODO:item: 1) Tarball size in moonbase/lunar
sofar/TODO:item: add cpan:// urls and see if it can be made working with a default_cpan_build or something like that
sofar/TODO:item: add a uniform verification scheme that allows us to use one scheme to verify the valitidy of sourcefiles, possible syntax would be a DETAILS entry (SOURCE_VFY[0]=MD5:1a9e1f6c2c4b5a1d2827312) (SOURCE_VFY[1]=GPG:url-to-asc-file)
Modified 200307202007
elaine/TODO:item: Start own TODO
elaine/TODO:item: Core documents, functions, subroutines, module design
elaine/TODO:item: kernel code hash generation tool
elaine/TODO:item: Website re-design  
elaine/TODO:item: Selinux module/policy & metadata tools/config
elaine/TODO:item: NPTL module post-crash xxx
elaine/TODO:item: coalesce individual TODO's into master && perhaps add to private web
evildrew/TODO:item: 1. (Priority) Installation manual -- Handy guide to get people through the install and up and running.
evildrew/TODO:item: 2. Handy stuff on the command line -- Unique commands to lunar and how to use them to your advantage.
evildrew/TODO:item: 3. Core documentation -- The more serious version of #2.
nestu/TODO:item: 1) Tarball size in moonbase/lunar
sofar/TODO:item: add cpan:// urls and see if it can be made working with a default_cpan_build or something like that
sofar/TODO:item: add a uniform verification scheme that allows us to use one scheme to verify the valitidy of sourcefiles, possible syntax would be a DETAILS entry (SOURCE_VFY[0]=MD5:1a9e1f6c2c4b5a1d2827312) (SOURCE_VFY[1]=GPG:url-to-asc-file)