>>>> On Sun, 09 Jun 2002 19:52:14 +1000, Steve Youngs
<youngs(a)xemacs.org> said:
SY> |--==> "JL" == James LewisMoss <dres(a)lewismoss.org> writes:
>>>>>> On Sun, 09 Jun 2002 09:43:52 +1000, Steve
Youngs
>>>>>> <youngs(a)xemacs.org> said:
SY> James, can you send
me a copy of your "ad-hoc" system? I can see
SY> if it's missing anything. But if I were you I'd...
JL> It basically consists of doing one of three things:
JL> 1) If a Makefile was distributed in the package use it (often
JL> with a
JL> few minor changes).
SY> I don't think there are any packages in this category are there?
There are a few with things like Makefile.example.
JL> 2) If it doesn't compile with 3 add a script that seems to
JL> compile
JL> things ok (the only cases so far are the one starting this
JL> conversation (unicode compile) and a few packages that seem to
JL> prefer that their file get compiled separately (calc) or need a
JL> particular file loaded first (can't remember example)).
JL> 3) Run xemacs -batch -f batch-byte-compile *.el (I'm doing this
JL> from
JL> memory so ignore any mistakes).
SY> Both of these seem very prone to danger. We go to fair lengths
SY> with setting up the build environment for building packages. In
SY> a nutshell, the safest way to build packages is from within a
SY> _complete_ packages CVS tree.
OK.
SJT> Use the CVS checked-out source.
SY> The Steves are in agreement. :-)
JL> This seems a reasonable choice. I'll look into doing this.
JL> Actually it'd be nice to be able to do it more often than sumos
JL> come out.
SY> Well when I've got my act together I do make public package
SY> releases between Sumos. Subscribe to xemacs-announce, any
SY> announcement that I send there is for stuff that's going public
SY> (ie, not Pre-Release).
I see them.
JL> The only thing that makes me nervous about this is getting
JL> something I shouldn't and distributing it in debian and the
JL> problems getting to you rather than me.
SY> What do you do to combat this now?
Only release a new xemacs package when a new sumo comes out. I've
been meaning to release for each new set of packages, but it's complex
and I haven't found the time to make sure everything works well yet.
JL> Is there a cvs tag I can look at across each package that means
JL> stable?
SY> Whenever I release a package I tag CVS.
SY> For example:
SY> vm-7.07-pkg.tar.gz has the tag vm-7_07
SY> gnus-1.61-pkg.tar.gz has the tag gnus-1_61
OK.
Thanks
Jim
--
@James LewisMoss <dres(a)lewismoss.org> | Blessed Be!
@
http://www.lewismoss.org/~dres | Linux is kewl!
@"Argue for your limitations and sure enough, they're yours." Bach