[Lunar-bugs] [bug] lunar rebuild causes update of module versions instead of using current versions

[sofar]

 Project:      lunar-linux
 ID:           
 Version:      <none>
 Component:    theedge (core tools)
 Category:     bug reports
 Priority:     normal
-Assigned to:  
+Assigned to:  sofar
 Reported by:  Arnald
 Updated by:   sofar
-Status:       active
+Status:       fixed

* moonbase is now omitted during 'rebuild'
* also $LUNAR_MODULE is removed from the queue

sofar



Previous comments:
------------------------------------------------------------------------

Sat, 07/10/2004 - 11:35 : Arnald

As I understand it, and as I believe has historically been the case, the
lunar rebuild command is intended to perform a rebuild of the lunar
installation as it currently stands, preserving current software
versions.  Other methods exist for performing upgrades.

The rebuild function in main.lunar builds a list of modules using the
command:

LIST=$(grep ":installed:" $MODULE_STATUS | cut -d: -f1)

which will clearly include the moonbase module.  The latest moonbase is
therefore installed, possibly indicating new versions of some modules,
which are subsequently upgraded.

If the moonbase module were explicitly stripped from this list, eg:

LIST=$(grep ":installed:" $MODULE_STATUS | cut -d: -f1 | grep -v
moonbase)

Then no network activity would occur; moonbase would not be upgraded,
and the system would be rebuilt with current versions in place as is, I
believe, the intention.





-- 
View: http://lunar-linux.org/?q=node/view/341
Edit: http://lunar-linux.org/?q=project/comments/add/341