Jon Nall
2003-07-31 14:56:54 UTC
hi all.
i just wanted to write a quick note updating people on the status of
porteus. we've accomplished a great deal in the past month. for those
that don't know, the current phase we're in involves modifying the
portage system to serve as a testbed for new ideas. so where are we?
* 100% documentation of the portage API. This was a huge effort and i'd
like to thank those who helped (slowhog, h22113, rossgir, and caustin).
The documentation was written in PyDoc format which can be parsed into
HTML. I hope to have this on a webpage sometime soon.
* Test harness. galak has done a great job getting a test harness in
place. it already found a portage bug! The harness is based on the
unittest module and a handful of API calls are currently tested.
* Tree overlay support. porteus can sync from multiple overlays and can
find/process builds in each of the overlays.
* SVN support. porteus can sync from subversion trees.
* Split ebuild format. porteus supports the proposed split ebuild
format. This requires some explanation. An idea was proposed to split
ebuilds into a generic portion and an architecture specific portion. the
generic portion might make calls into the architecture-specific portion
for things like patching sources, etc. the architecture-specific portion
can override any variables or functions it deems necessary. technically,
this is nearly identical to eclasses. This has implications to the
subversion tree layout which i won't get into here as i understand it's
going to be addressed in a forthcoming email.
so what's next? currently use cases and requirements are being gathered
for porteus. once those are aggregated, i will begin drafting a proposal
for the next generation of porteus. in parallel work will commence on a
from-scratch prototype.
thanks!
nall.
i just wanted to write a quick note updating people on the status of
porteus. we've accomplished a great deal in the past month. for those
that don't know, the current phase we're in involves modifying the
portage system to serve as a testbed for new ideas. so where are we?
* 100% documentation of the portage API. This was a huge effort and i'd
like to thank those who helped (slowhog, h22113, rossgir, and caustin).
The documentation was written in PyDoc format which can be parsed into
HTML. I hope to have this on a webpage sometime soon.
* Test harness. galak has done a great job getting a test harness in
place. it already found a portage bug! The harness is based on the
unittest module and a handful of API calls are currently tested.
* Tree overlay support. porteus can sync from multiple overlays and can
find/process builds in each of the overlays.
* SVN support. porteus can sync from subversion trees.
* Split ebuild format. porteus supports the proposed split ebuild
format. This requires some explanation. An idea was proposed to split
ebuilds into a generic portion and an architecture specific portion. the
generic portion might make calls into the architecture-specific portion
for things like patching sources, etc. the architecture-specific portion
can override any variables or functions it deems necessary. technically,
this is nearly identical to eclasses. This has implications to the
subversion tree layout which i won't get into here as i understand it's
going to be addressed in a forthcoming email.
so what's next? currently use cases and requirements are being gathered
for porteus. once those are aggregated, i will begin drafting a proposal
for the next generation of porteus. in parallel work will commence on a
from-scratch prototype.
thanks!
nall.