Re: xoobr: whoa there baby! Not so fast!

|--==> "Jake" == Jake Colman <jake.colman(a)xemacs.org&gt; writes: SY> 1) Distribute xoobr as fully self-contained source tarball SY> within the OO-Browser package. (*NOT IN CORE*) Jake> Can you send instructions on how to do this? Does the Jake> packages system support inclusion of a tarball together Jake> with the package? All you need to do is decide where you want the tarball to end up once somebody has installed OO-Browser, and then add the appropriate line to the package's Makefile: If you want the xoobr tarball to sit in OO-Browser's lisp directory, 'xemacs-packages/lisp/oo-browser/' just add this to OO-Browser's Makefile: EXTRA_SOURCES = xoobr.tar.gz Of if you want it in 'xemacs-packages/etc/oo-browser/' DATA_FILES = xoobr.tar.gz DATA_DEST = $(PACKAGE) Or 'xemacs-packages/etc/oo-browser/xoobr/' DATA_FILES = xoobr.tar.gz DATA_DEST = $(PACKAGE)/xoobr Etc, etc, etc. I don't really have a preference for where inside of the OO-Browser package that xoobr resides. Jake> What about if a different tarball is required for unix vs Jake> windows? Why would that be necessary? Surely a source tarball is a source tarball is a source tarball? Or does that piece of crap that microsuck calls an OS have a different idea as to what source is? SY> 2) Port xoobr to elisp and make it part of OO-Browser. (this SY> would be my preference) Jake> Sorry, this would be beyond my current skills and available Jake> time. That's a shame, oh well, maybe someone down the track will look at it and say "I bet I could do that in lisp..." :-) -- |---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---| | XEmacs - The only _______ you'll ever need. | | Fill in the blank, yes, it's THAT good! | |------------------------------------&lt;youngs(a)xemacs.org&gt;---|