Norman wrote:
> Anyone who wants to work on the software will have to work on the
> repository, which means checking out the application, reading the
> README, and typing `make world', or at least `make .../manifests/foo'
> to configure and build foo and all its dependencies. So more
> sophisticated users will need to use anonymous CVS to get the stuff
Absolutely, if they want access to bleeding edge development as a user
than they should be savvy enough to use anonymous CVS access. If not, they
should stick with the releases.
> 2. The distribution tarballs will have dependencies between them -- in
> order to build one tarball you might need to have built and installed
> another.
Which is where RPM (et al.) wrapped tarballs come in (which is now even
more trivial than it was before under the old build system, which was
pretty trivial, I still don't understand why Martin never did anythnig
with the work Tim and I did on RPM'ing /stardev, ah well, water under the
bridge).
> 3. Mark is correct in saying that the distribution targets have not
> been much tested, though I think David is releasing AST tarballs this
> way (correct?). There's not an awful lot to test -- if you do "make
> dist" you should get a tarball which is mostly correct, and fixing
> which is just a matter of adding a couple of dist_ or nodist_ prefixes
> here and there, or adding EXTRA_DIST values.
I get
make: *** No rule to make target '.htx_tar', needed my 'distdir'. Stop.
under all circumstances (ie all of the applciations I've tried a
make dist on give this error, e.g. photom, kappa). On the other hand
AST does seem to build a release tarball. Is Dave doing something
different here, or is this an applications/libraries thing?
Al.
|