Re: What about CONS?

(Sorry for slow response -- pre-vacation panic...)

Harlan writes:

> Anybody given any thought to allowing CONS as an alternative choice to
> "make" for some packages?

Not me; but I don't foresee a problem:

   % ark package reveal CONS--x.y.z # install CONS as normal...
   % edit <site>/host/ALL.xml # record that cons is avail. for all hosts (optional)
   % ark package reveal random-package-that-uses-CONS
   % etc.

> I'm asking because for certain packages, certain people want to use a CVS
> repo as the "place" to get their software from as opposed to a tarball, and
> CONS seems to have support for this.

No problem with that...  I would note that the current Sidai
stuff is about 15 lines of shell script short of doing
that.  Where you might currently have

   <prototype team="sidai" name="GNU" />
   <prototype team="."     name="ALL" />

you precede that with

   <prototype team="sidai" name="cvs-source" />

Then, in sidai/package/cvs-source.xml, all you need to do is
heave in something like (over-simplified...)

  <assemble-source>
    <param name="CVS">@host:CVS@</param>
  <code>
  cd $PKG_BUILD_DIR/some-subdir
  $CVS -q update -d -P
  </code>
  </assemble-source>

As I'm likely to say again, the ARK stuff simply gives you a
way to describe what you want to do -- it in no way
constrains what you choose to do.

Will