Perl portability
The Hermit Hacker
scrappy at hub.org
Thu Sep 9 05:46:31 UTC 1999
On 8 Sep 1999, Russ Allbery wrote:
> The Hermit Hacker <scrappy at hub.org> writes:
> > On 8 Sep 1999, Russ Allbery wrote:
>
> >> One fix is to re-order the -I options when compiling perl.c and hope
> >> that that will cause compilers to grab Perl's first. Another fix (and
> >> a slightly cleaner one) would be to rename include/patchlevel.h to
> >> something like include/innversion.h.
>
> >> Preferences?
>
> > innversion.h or just version.h sounds reasonable...
>
> The advantage of innversion.h over version.h is that if we link against
> something else embedded and it decides to use version.h instead of
> patchlevel.h, we don't end up with the same problem. If something else
> uses innversion.h, we'll yell at them. :)
>
> James, will renaming it break anything?
>
> (And what's the preferred renaming method? Adding a new file and cvs
> removing the old one, or copying the RCS file inside the CVS repository
> and then cvs removing the old name?)
So that we maintain the history (unless this absolutely doesn't matter?
*raised eyebrow*), I can login and just move the file around inside the
repository...
My thought is that retaining the 'history' of patchlevel.h probably
doesn't matter though, does it?
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy at hub.org secondary: scrappy@{freebsd|postgresql}.org
More information about the inn-workers
mailing list