Re: tlug: Perl linked against libc 5 & 6 on TL2.0J ??

[Rex Walters <rex@example.com>]

>>>>> Andrew S. Howell writes:  (on 16 Nov 98)

> What, you mean you only have a single user license for RPM and you're
> using it all over the network? Shame on you! :)

[For the humor impaired: RPM is GPL'd.]

Nah, I mean it works great on an Auspex, but I can't release it.  C'est
la vie. (sp?)  Basically the same as porting to SunOS 4.X with only trivial
modifications.

> I tried building it on Solaris 2.5.1, but it needed db.h. I made a
> rather lame attempt to locate a "libdb" on the web, but didn't turn up
> anything. You wouldn't happen to have a URL would you?

Not handy, but a search for "Berkeley DB" should find it.  Let me know if
you still can't find it, and I'll dig it up.  I think the URL is in one
of the README files or at the www.rpm.org website.

Anyway, I vaguely remember something in the RPM documentation talking
about how to remove references to db.h (comment out a couple lesser used
commands).

> I'm not convinced that binary packages as such are 'evil'. I think
> where you get in trouble is when they are used without knowing if they
> apply to your system or not. If I take a rpm for RH 4.2 and install it
> on 5.2, I deserve whatever I get ( or don't get as the case may be ).

Prescience is always difficult when building an rpm, but if you have the
libc5 libraries on your system I think RPM *should* let you install a
4.2 rpm on a RH5.2 system.  If it doesn't work, a well-built rpm is easy
to de-install.

> My usual ploy with most stuff is that if all I had to do was
> "configure; make; make install", then I don't bother to document it.

Yeah, me too.  Unfortunately I always start going "well it was only one
or two little changes, I'll remember that"....

> Well, I wonder to what extent the SPEC files are reusable? In other
> words, would it make sense to just keep around the SPEC files, without
> the source? My thinking is that one could then have semi-automated
> builds, or at least capture what was needed for a particular version.

Well, you need the spec file AND any patches you've made of course.  If
the code doesn't change too much from release to release, I think the
spec files are quite reuseable.  Even if you can't use it verbatim, it
gives you quite a bit to go on.

Regards,
-- 
Rex
----------------------------------------------------------------
Next Nomikai: 20 November, 19:30   Tengu TokyoEkiMae 03-3275-3691
Next Technical Meeting: 12 December, 12:30 HSBC Securities Office
----------------------------------------------------------------
more info: http://tlug.linux.or.jp Sponsors: PHT, HSBC Securities