>>>>> "WHN" == William Harold Newman <william.newman@...> writes:
WHN> On Wed, Feb 01, 2006 at 02:04:23PM -0600, rpgoldman@... wrote:
>> >>>>> "WHN" == William Harold Newman <william.newman@...> writes:
WHN> On Mon, Jan 30, 2006 at 07:56:55AM -0800, Robert P. Goldman wrote:
>> >> I use Mandriva (formerly Mandrake) Linux. Mandriva has
>> >> slightly different RPM packaging constraints that RedHat
>> >> (but close).
>> >> I've made srpms for Mandriva for SBCL, taking Dave Roberts'
>> >> stuff as a starting point. Would you like me to send them
>> >> to you for inclusion in the Sourceforge project?
WHN> Packages for Mandriva do sound useful. Is it your intent to do it just
WHN> this once, or to continue doing it regularly for many releases?
WHN> (Either is useful; having even one old binary version available lets
WHN> users compile a new version from source for themselves.)
>> I was thinking of continuing to do this on a fairly regular basis
>> (possibly being a parasite on Dave Roberts' continuing efforts).
>> 0.9.8 seems to be working fine for me. 0.9.9 I'm having trouble
>> I was going to just put them up on my website, but my ISP beat me with
>> a club... :-)
>> Not unreasonably! I put up patched xemacs rpms at the same time!
WHN> For what it's worth, your inadequate bandwidth for xemacs could be
WHN> entirely adequate for sbcl: I would be pretty tickled to find that
WHN> there was even 5% as much demand for sbcl RPMs as for xemacs RPMs, but
WHN> I'm guessing it won't happen.:-| However, it doesn't sound as though
WHN> it would be your first choice to host the RPMs yourself even if
WHN> bandwidth weren't an issue, and I don't mind putting your RPMs up
WHN> until I probably get impatient and just give you write access. If
WHN> that's what you'd like, tell us what public key information to
WHN> advertise for any signatures you associated with them; also ideally
WHN> give me URL where I can get my copy, or if your ISP situation is too
WHN> hopelessly screwed up to do that, I can send you instructions on
WHN> FTPing a copy into the public/incoming/ directory on an appropriate
WHN> sf.net server.
It was actually storage, rather than bandwidth. I can probably make
the sbcl ones fit temporarily. I'll send you a link separately; I
don't need to shout it out to the list...
WHN> [how to identify them as not-quite-Redhat packages?]
>> They look like this;
>> I think you can count on the 'mdk' always being there (it might change
>> to 'mdv,' at some point).
WHN> OK. Ideally I would wish the names were more self-explanatory, perhaps
WHN> with the full word "mandriva" in there somewhere, especially since
WHN> Sourceforge in their wisdom limits file type type information to
WHN> multiple choices which don't include "RPM for Mandriva Linux" as a
WHN> choice. I can live with sbcl-0.9.8-0.1-20060mdk.i586.rpm,
WHN> but I propose to wait for a few days to see if anyone has any other
WHN> suggestions, on names or anything else ("Here's how [some enormously
WHN> successful free s/w project] does it, and it's worked flawlessly
WHN> [since well before the big bang]" for example.:-) before putting
WHN> up your first mdk.rpm.
This really isn't an area where there's a lot of choice. The Mandriva
RPM macros automagically generate the "mdk." It's canonical and would
cause confusion if it were missing.
I will also see if I can get these snarfed into Mandriva's "contrib"
process. In that case we could drop putting them on Sourceforge
altogether. I'm not sure how open they would be to that.