>From sfwnv-discuss-bounces at opensolaris.org Tue Sep 25 20:42:43 2007
>> I think 'c' is best for now. I didn't know there was a private
>> headers rule in tcl, but if it only installs headers and not
>> source then it doesn't fix my main concern about tcl/tk, which is
>> things that reach into their source tree and use the headers
>> and C files. We probably should just ship their source with the
>> packages and be done with it though.
>>
>
>Accepted.
>I didnt see the latest changes in CCD since I picked the tarball
>(quite old). Now I have picked from the snv. Will point it to $(SRC)
>
the changes in the ccd to cope with the tcl/tk upgrade aren't there yet,
as how to deal with needing the tcl/tk source hasn't quite been
decided. though I haven't lost sleep over that but I may well soon.
>> so this confuses me - I don't know why this patch is there (tail has
>> always been in /usr/bin), so I assume it wanted the one in /opt/sfw/bin
>> because that was GNU tail. Which it may still want and should point to
>> /usr/gnu/bin/tail instead. I can't find any more information other than
>> it was added during the update to 5.39 and created by, I think,
>> Paul Cunningham, so perhaps he can add something here :)
>>
>
>Yes, I meant /opt/sfw/bin/tail.
>B72 doesn't have the sfw paths (/opt/sfw, /usr/sfw,...) There is no
Hmm if it's a build issue then it should have shown up in
your builds. Perhaps we fixed tail since that change - hopefully
paul will respond and know. You might go ask on the companion-discuss
alias since I know he hangs out there. But anyway...
for tail you mean. /usr/sfw has been there a while and /opt/sfw
isn't part of Solaris.
/usr/gnu/bin/tail should be there as of 67 though, where
SUNWgnu-coreutils appeared. Though not sure if you need to install
the All cluster to get it (without manual pkgadd).
Though if you don't need it that's great, I just want to make
sure there is no regression or now, a build failure.
>> If it does need that then the expect package will need to
>> depend on SUNWgnu-coreutils.
>>
>
>Not quite. tail command is a build requirement and is not a
>requirement for installation & working of expect.
>Is there a way to specify build requirements anywhere ?
ah ok. No, other than a flag day saying 'you need build XXX of
Solaris to build sfw now. Or go add package YYY from build XXX
first.' You're supposed to be building N on no later than N-2 but
of course that doesn't always happen :)
>> > 5. Modify Makefile in pkgdefs so that expect package gets created.
>> > I have named the package as SUNWexpect.
>> > patch: Expect_SFW_PackageCreation_Integration.diff
>>
>> whoever sponsers this will need to register that package name
>> and do the package rti's and such.
>>
>> SUNWexpect doesn't seem to be taken so that's good.
>>
>
>Do I need to do anything to initiate this?
You cannot as it's an internal RE thing. I just mentioned it
for whoever sponsor's this, and since I looked in case
somebody had taken that name (the RE package registry covers
more than just Solaris I believe, so it could have been
taken by some other product).
>> well and maybe the man pages need a 'share' in there.
>>
>
>Ok.
>When to use /usr/man and when to use /usr/share/man ?
For bundled things (sfw) /usr/share/man is where man pages
go. /usr/man is just a link, which you can't break by
listing /usr/man as a directory in your package. The ccd
had its own rules created by someone long long ago, who
surely won't admit to not worrying about people wanting
to share man pages :)
Mike
