I'm starting to look at implementing the aegis source backend and I see two possibility:
* use the native replication method (aedist -replay) and then make tailor extract changesets from the local repository. Looking at tailor source it seems to me the approach used by others source backends. It's not really difficult to do that also for aegis except for the time that may be needed to apply a changeset locally: as an example each change committed in the aegis 4.22 stable branch took not less than 2 hours to be "commited". The reason for such a long time is due to the need to compile aegis *twice* and run the full regression suite *twice* (development and integration). With the current development branch the time needed to commit a change-set is measured in minutes (>= 5min) but not in seconds. I'm not sure a user that want to extract a project from aegis will be happy to wait so much time. * the alternative approach is to replicate much of the work of aedist -rec to extract the content of a change-set from an aedist archive skipping the build and test stages. The aedist archive is a simple bzipped cpio file that contains metadata, complete source of the files and patches. It's a bit more difficult wrt the previous approach because the file containing the metadata need to be parsed, but not too difficult. Which one is the way to go (from a tailor user POV)? -- Walter Franzini http://aegis.stepbuild.org/ PGP Public key ID: 1024D/CB3FEB43 Key fingerprint : FA26 C33B CAFF 7848 EFEB 7327 96AA 2D57 CB3F EB43 Key server : http://www.keyserver.net
pgpOYUDvmTihw.pgp
Description: PGP signature
_______________________________________________ Tailor mailing list [email protected] http://lists.zooko.com/mailman/listinfo/tailor
