Re: packages from CVS, not tarball

Harlan asks:

> There are some packages I use that come from CVS repositories instead of
> tarballs.
> 
> As such, they are being updated dynamically, and will have changing version
> numbers.
> 
> What's a good way to handle this case?

I don't know about "good", but this is a fairly common thing
in glasli1/sidai land...  Packages like sys-cron-config are
also changing over time.  Another one that Matt was doing
for a while was mozilla-nightly.

Version numbers have been optional since "ARK2".  (Before
that, we used the pseudo-version number 'CURRENT'.)

Anyway, for this kind of thing, I use the 'ark-invasive'
script (welcome a better name), which is in
sidai/ark-pkg-mgmt/.  If you do 'ark-invasive
sys-cron-config', it rolls back the state info, then does an
'ark package deploy ...' to roll it forward again.

That script is specifically intended to work with "diffing
deploy" packages (the 'deploy' method does a diff between
deployed and revealed, which you inspect before doing 'ark
package reveal ...'); a slight variant might be required for
a grab-cvs-and-rebuild scenario.

Will