[Linux-ha-dev] heartbeat package name [Was: Re: Linux-HA-Dev Subscribe Notification]
jtingiris at bellsouth.net
Wed Nov 2 19:14:44 MST 2005
David Lee wrote:
> It works for me: Solaris 8 and Solaris 9. (It worked back then, and
> I've just re-tried in direct response to your email: still OK.)
> But if I recall correctly, you are on Solaris 10, aren't you? (Alas
> our own (tiny) S10 environment has a separate (non-pkg, non-heartbeat)
> difficulty which is preventing me from building heartbeat (and other
> apps) at present, so I am unable to attempt to reproduce on S10.
Yes, this is on Solaris 10.
> So might this be S10 pkg having additional restrictions such as not
> allowing any upper-case chars following the first lower-case?
"OPENHA" works, "openha" works, "OpenHA" does not work
> (Note that you are probably the first person in the world to be
> attempting "make pkg" on S10. So your findings are important.)
> Continuing the assumption that you are S10, and that this might be
> 1. Do you have an S8 or S9 you could try this on?
Yes, but my build stuff is all on 10 (and I wasn't really planning to go
back to 8). I will get something set up though and give it a go ...
> 2. Can you see anything in S10 documentation which might indicate an
> added (S10) restriction on pkg names?
Nope, and I really looked. All I found today was that PKG can (now) be
32 characters long. There are only slight references are to "best
practices", and "up to 4 character company name, such as the stock
symbol". And that Solaris uses SVR4 pkg rules. I was going to look for
an RFC or something, next.
> 3. On S10, could you try "ConfigureMe ... --with-pkgname=XXXxxx" for a
> few lc/uc-mixtures of "XXXxxx". (*)
BTW, ConfigureMe just doesn't work for me on sol10 (with 2.0.2, or
HEAD). Now I have a home grown build script that makes (and packages)
it (using ./configure, make install, etc.). I really wanted to use the
sol10 /usr/sfw tools (e.g. SUNWgcc 3.4.3) and ultimately have heartbeat
install in /opt/PKG (prior to this thread). Rather than modifying
ConfigureMe right away, it was just easier to encapsulate the steps I
needed into something completely different. I figured once I worked out
the quirks and had something tangible (from a binary perspective) I
would have a better grasp on how to integrate things. A different
thread, maybe ...
> If not, then during the next couple of days, I'll see if I can grab a
> few minutes to try to specify and build a trivial pkg (which wouldn't
> involve our other little local difficulties) to investigate possible
> S10-isms in the name.
Definitely a different thread ... lots of new details.
>> What about OHAheartbeat?
> In 1.2.x we had used a simple "OPENHA".
FYI "OHAheartbeat" works, too
> (*) This is where having a srcdir and (possibly multiple) separate
> builddir can be very useful! E.g. parallel:
> ( mkdir build_x; cd build_x; ../ConfigureMe ...
> --with-pkgname=XXXxxx )
> ( mkdir build_y; cd build_y; ../ConfigureMe ...
> --with-pkgname=yyyYYY )
> ( mkdir build_z; cd build_z; ../ConfigureMe ...
> --with-pkgname=ZzZzZz )
I getcha ...
More information about the Linux-HA-Dev