From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: auctex-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: CVS repository synchronization for RefTeX
Date: Mon, 01 Jan 2007 18:59:45 +0100 [thread overview]
Message-ID: <v9mz52fx0u.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87k607yi0e.fsf@neutrino.caeruleus.net> (Ralf Angeli's message of "Sun\, 31 Dec 2006 20\:36\:49 +0100")
On Sun, Dec 31 2006, Ralf Angeli wrote:
> * Reiner Steib (2006-12-30) writes:
>> When using admin/reftex/*, I don't see that it's much harder than in a
>> separate repository.
>
> I'm not sure if I understood correctly. You mean to put only the
> build files, auxiliary files (README, INSTALL, etc.) and ChangeLog
> into admin/reftex?
Yes. (WRT ChangeLog, see below.)
>> With Richard's okay to a RefTeX-only branch in Emacs CVS, this sounds
>> like a good solution to me.
>
> What I dislike about it is that the files will be scattered throughout
> Emacs' repository. This makes fetching the "package" RefTeX from CVS
> much more complicated. And with the branch it would get even harder
> if people want to fetch a development version.
If I understand Stefan correctly, it's possible to create a branch
with just the RefTeX relevant files. So it should be possible to "cvs
co -t reftex_devel ...", i.e. only check out RefTeX relevant files
from Emacs CVS. If not with this command, it should be simple to make
such a target in admin/reftex/Makefile nevertheless (cvs [...] co
emacs/admin/reftex/ && cd emacs/admin/reftex/ && make fetch-files).
> Also stuff like `C-x 4 a' won't work with such a file layout and a
> single ChangeLog file.
A the changes would be done in the Emacs CVS directory layout, also
these ChangeLog files (lisp/ChangeLog, man/ChangeLog) should be used.
No problem with `C-x 4 a'.
I played a bit with the following[1] sketch of admin/reftex/Makefile.
Using grep-changelog we can build RefTeX-only ChangeLog files (some
entries are not extracted correctly, but this could be remediated by
re-writing the corresponding entries in the original ChangeLog files
(or improving grep-changelog?).
Bye, Reiner.
[1]
--8<---------------cut here---------------start------------->8---
base=../..
grepcl=$(base)/lib-src/grep-changelog --text=reftex
ChangeLogs: lisp/ChangeLog texi/ChangeLog
lisp/ChangeLog: $(base)/lisp/ChangeLog
$(grepcl) $< | sed -e 's,textmodes/reftex,reftex,g' > $@
texi/ChangeLog: $(base)/man/ChangeLog
$(grepcl) $< > $@
clone-files:
cp -p $(base)/lisp/textmodes/reftex*.el lisp/
cp -p $(base)/man/reftex.texi texi/
clean:
rm lisp/ChangeLog texi/ChangeLog
--8<---------------cut here---------------end--------------->8---
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2007-01-01 17:59 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 22:53 CVS repository synchronization for RefTeX Ralf Angeli
2006-12-29 22:04 ` Stefan Monnier
2006-12-29 23:43 ` Ralf Angeli
2006-12-30 14:20 ` Eli Zaretskii
2006-12-30 15:08 ` Ralf Angeli
2006-12-30 15:20 ` Eli Zaretskii
2006-12-30 16:01 ` Ralf Angeli
2006-12-30 16:47 ` Carsten Dominik
2006-12-30 18:03 ` Eli Zaretskii
2006-12-30 18:50 ` Ralf Angeli
2006-12-30 19:03 ` Eli Zaretskii
2006-12-30 19:18 ` Ralf Angeli
2006-12-31 1:46 ` Richard Stallman
2006-12-30 21:28 ` Alan Shutko
2006-12-30 21:55 ` Reiner Steib
2006-12-31 22:27 ` Giorgos Keramidas
2006-12-31 23:57 ` Ralf Angeli
2007-01-01 7:09 ` Ways of keeping Emacs 22 and external projects in sync (was: CVS repository synchronization for RefTeX) Michael Olson
2007-01-01 15:21 ` Ways of keeping Emacs 22 and external projects in sync Ralf Angeli
2007-01-01 17:59 ` Reiner Steib
2007-01-01 18:36 ` Giorgos Keramidas
2007-01-03 10:43 ` Yavor Doganov
2007-01-03 18:32 ` Michael Olson
2007-01-03 18:29 ` Michael Olson
2007-01-03 19:53 ` Ralf Angeli
2007-01-03 22:37 ` Michael Olson
2007-01-01 18:20 ` Ways of keeping Emacs 22 and external projects in sync (was: CVS repository synchronization for RefTeX) Giorgos Keramidas
2007-01-01 21:56 ` CVS repository synchronization for RefTeX Richard Stallman
2006-12-30 18:23 ` Richard Stallman
2006-12-30 18:39 ` Ralf Angeli
2006-12-31 1:47 ` Richard Stallman
2007-01-01 16:01 ` David Kastrup
2007-01-02 3:09 ` Richard Stallman
2007-01-02 7:43 ` David Kastrup
2007-01-02 21:24 ` Richard Stallman
2007-01-03 8:48 ` David Kastrup
2007-01-04 2:31 ` Richard Stallman
2007-01-04 21:51 ` David Kastrup
2007-01-06 2:54 ` Richard Stallman
2007-01-06 9:14 ` David Kastrup
2006-12-30 21:54 ` Reiner Steib
2006-12-31 19:36 ` Ralf Angeli
2007-01-01 17:59 ` Reiner Steib [this message]
2007-01-01 19:12 ` Ralf Angeli
2006-12-30 22:07 ` Stefan Monnier
2006-12-29 22:59 ` Richard Stallman
2006-12-30 17:00 ` David Kastrup
2007-01-07 21:42 ` Bill Wohler
2007-01-08 19:25 ` [AUCTeX-devel] " Ralf Angeli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=v9mz52fx0u.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=auctex-devel@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).