Vladimir Marek wrote:
> Hi,
>
> While looking at sfw gate, few questions came to my mind.
>
> 1) Why are usr/src/cmd/Makefile.targ and /usr/src/lib/Makefile.targ
> different ? Libraries could also use the unpacking and patching stuff
> from cmd/Makefile.targ.
>
{cmd|lib}/Makefile.targ originated in ON and have a series of different
targets in them. There are a few targets in cmd/Makefile.targ that
should probably move up to Makefile.master and be used by everyone. The
unpacking and patching (and eventually download) targets come to mind.
I know that when I integrated them into cmd/Makefile.targ, there was a
conflict with something in usr/src/lib and that's why it isn't in
Makefile.master yet.
>
> 2) Looking at usr/src/cmd/Makefile.targ, it seems that there's some work
> on separating different package statuses and describing process how to
> go from one status to another. For example .patched and .unpacked. Is
> this somewhere documented ?
>
It's not documented and needs to be. I started working on templates for
Makefile.sfw, METADATA, and packaging related bits a while back, but it
seems like I never can get back to them. I would like to complete them,
put them out for review, document the various targets and get components
to start moving to them. You will also find a completely undocumented
program in tools/pkgtemplate.pl. It can save you considerable time in
packaging a component. If you build a component and install it
somewhere (DESTDIR=/tmp/foo), you can use pkgtemplate.pl to generate
package(s) automatically. It matches owner/group/mode with the package
db on the system it's running on and does some other things to make life
easier. You still have to audit the results, but it beats packaging
1000 files by hand.
>
> 3) Do we have some sort of wiki where we can document things ? I manage
> several wikis in SWAN, but they are not publicly available. I think that
> describing the package statuses is very important step to give all the
> packages similar look.
>
This is something that I have suggested to management that we need to
do. There is documentation on the gate machine, but it could stand some
updating and I would love to see it outside in a Wiki so that others can
get involved with it.
>
> 4) Why there's often touch to configure ?
> gtar xzf XXX.tar.gz
> touch configure
>
The touch is because the timestamp on configure is going to be older
than the tarball timestamp.
-Norm
