Project Entropy: another milestone reached
With the launch of the miniEdition, we started to (quite) silently ship a small emerge wrapper called “binmerge” that interfaces to our Alpha release Binary Hosting. Now, I’ve just finished the Activator code section that manages the syncronization between the Entropy locally built binaries and the mirrors. But it’s not the only thing that happened this week to the sources:
- Enzyme is now able to be easily interfaced to a distcc infrastructure (I am happy to compile Qt 3.3.8 in 5 minutes) and supports add/remove, enable/disable, show options
- Enzyme is now able to search packages inside the portage tree and actually takes 1/8 of the time if compared to the classical “emerge -s”
- Enzyme now supports the Portage ever seen option “–skip=N”, the successor of –skipfirst
- Activator now supports the lock/unlock functions for the metadata database, including the option to only lock/unlock the download of data by the future clients
- Activator now supports the visualization of the lock status of the databases
- Activator now supports –ask and –pretend for the packages tool
The amazing thing is that I developed all the infrastructure for the maximum flexibility and speed. I think that I still need a month to stabilize all the new code and then, we can start to talk about a binary packages client. I can’t wait !