> When I sat down to send out Uncle G.'s patches to the debian
> developers I realized that the patches really only apply to a moving
> target. What I mean, is that they will only apply to current snapshots
> (i.e. Jun 23's), but not to the older 6.5.1 release. By giving out these
> patches, and telling them to just go and get a snapshot, they might end up
> getting the snapshot on a day that pgsql is broken, or the patch will no
> longer apply. The best solution I can think of is just to take one of the
> snapshots (today's if it works, testing it now, otherwise last Fridays),
> and setting it aside along with the patches in a seperate 'linux_alpha'
> directory so packagers can have something "non-moving" to package for
> thier distributions. Is this a good idea, or does someone have a better
> one?
I didn't realize that they weren't developed on v6.5.1 sources. That
is what I'll need to develop RPM patches. I'd suggest that we work
with the v6.5.1 tar file, unless we think that using this version is
unrealistic, in which case we are waiting for v6.6. As you point out,
a daily snapshot of almost any vintage should be suspect.
Lamar Owen is talking to RedHat about getting access to an Alpha
machine to help with RPM builds. If that pans out perhaps it will be a
good resource for us...
- Thomas
--
Thomas Lockhart lockhart@alumni.caltech.edu
South Pasadena, California
