Vladimir Marek wrote:
> Hi Norm,
>
> Thanks for the quick answer !
>
>
>
>>> While looking at sfw gate, few questions came to my 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.
>>
>
>
> If there is no CR for it, I'll create one. I think that we are closing
> to silent period before opensolaris, so maybe it's not good time to push
> those changes.
>
>
There is a CR for the prototype files
6684691 SFW gate should include templates
I figure that we can fix it at part of this CR.
>> I would like to complete them, put them out for review, document the
>> various targets and get components to start moving to them.
>>
>
> Do you have some rough skim ?
>
> make all = (download) -> unpack -> patch -> build -> post_build ?
> make install = install
>
> Makefiles can be incredibly powerful for this. Have you thought about a
> way for package to override default action ? Afaik you can't delete
> once defined rule in other makefile and if you create second rule, make
> reports something like " Too many rules defined for target ..."
>
The patching does this by defining $(PATCHES) in the Component
makefile.sfw and generating/using $(PATCH_STAMPS) in Makefile.targ,
though I suspect that there is a better way. I haven't had the time to
dig into it. I am going on vacation for a couple of weeks, but we can
sync up when I get back.
The basic flow is as follows, but it probably needs some work.
install: install-protofix
install-protofix: install-target install-cleanup
run protofix
install-target: all
run component install target (make DESTDIR=$(ROOT)
INSTALL=$(INSTALL_PROTO) install)
install-cleanup: install-target
remove any bits we don't wan from the proto area, add things
that are missing
all: $(VER)/config.status
build the component
$(VER)/config.status: $(VER)/configure
run configure
$(VER)/configure: $(VER)/.unpacked $(VER)/.patched
touch $@
$(VER)/.patched: $(VER)/.unpacked $(PATCH_STAMPS)
touch $@
$(VER)/.patched.%: Patches/%
apply patch
touch stamp ($@))
$(VER)/.unpacked: $(TARBALL)
unpack-archive $@
>>> 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.
>>
>
> Creating a space on wikis.sun.com comes to mind.
>
> http://wikis.sun.com/display/Help/How+To+Create+A+Wiki+Space
>
> I don't have much experience with it, so hopefully it does not suck too
> much.
>
>
I created a Wiki on Wikis.sun.com called SFWNotes. We need to start
populating it. Jim Walker and I have talked some about jumpstarting
this by moving a bunch of the Wiki that he and his group have been
working on outside.
-Norm
