Re: Q: Package system structure
|--==> "JF" == Jarl Friis <jarl(a)diku.dk> writes:
JF> The Makefile in the package must have three targets that just depend on
JF> other targets, I guess that 'binkit' is intended to make all binaries in
JF> the package (invoked by 'make bindist').
Correct.
JF> But what about 'srckit' target? does that some reflect what the
JF> often well known target 'clean' that is remove all created files
JF> to get back to the sourcecode? or what?
No, 'srckit' has nothing to do with the 'clean' target. 'srckit'
was
designed to build a tarball of the package's source tree. I think so
that people could have an alternative to CVS for getting hold of
package source. It's pretty well broken an unimplemented.
BTW, in case you thought otherwise, there is a 'clean' (and
'distclean') target. It is set in 'XEmacs.rules'.
JF> What about the target all, what is the conceptually big difference
JF> between all and binkit?
'all' shouldn't build tarballs. (from someone who only ever uses the
'distclean', 'autoloads', 'bindist' and 'install' targets
:-P)
JF> On the drawing the double-edged boxes are supposed to illustrate the parts
JF> that package authors have to worry about, and the single-edged boxes could
JF> (in principle) be considered black-boxes from a package authors point of
JF> view. Am I right about this?
The ascii art looked great! Pleasing to the eye, as well as informationally
correct.:-)
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|