Re: [patch] automatic loading of package-get-base
Greg Klanderman <greg(a)alphatech.com> writes in xemacs-beta(a)xemacs.org:
>>>>> "sb" == SL Baur
<steve(a)xemacs.org> writes:
sb>
sb> Greg Klanderman <greg(a)alphatech.com> writes in xemacs-beta(a)xemacs.org:
>> I'd like to change the format of the package index file
to
sb>
sb> That's fine with me. Do you wish this to happen immediately?
That would be ideal. Can you see my post about the format to
xemacs-patches - there are 2 options, one which requires changing
package-info.in for all packages but is a little cleaner. Let
me know which you prefer as soon as you can.
O.K. I'll check.
sb> I'm going to release 21.2-beta3 this afternoon/evening along with a
sb> handful of package updates for a full dose of new package UI testing.
Will you commit my package-get-base patches too?
Yes, the existence of your patches is the point of the release.
The package UI stuff is broken otherwise. Also Jan's "big
screwup
in package-ui" one. If so I am close to another patch that should
go in, depending on your choice above.
O.K.
sb> Why don't you fix up the latest package-index on ftp.xemacs.org, drop
sb> the modified copy in:
sb> ftp://altair.xemacs.org/incoming/
But it wouldn't contain the updates you're about to make, or
is that
just so you don't have to rebuild all packages?
I very much do not want to rebuild and reupload all packages. The
last time it took about 5 hours to upload, so modifications to
package-info.in files is out for this iteration. I mean building this
release under the old format, hack the old format package-index to the
new format and see how it works.
If you want I can run a keyboard macro across the new one you create
later, I've done it here. But I'd prefer it get created automatically
with the build process so that part also gets tested.
It will, but I want to see exactly what you want so I'm not generating
something bogus.