On Sat, Aug 30, 2003 at 08:57:36AM -0400, Neil Roeth wrote: > On Aug 30, Sven Luther ([EMAIL PROTECTED]) wrote: > > On Fri, Aug 29, 2003 at 08:30:38PM -0400, Neil Roeth wrote: > > > On Aug 29, Sven Luther ([EMAIL PROTECTED]) wrote: > > > > I have a package that installs a xemacs specific .el file, which > > > > naturally don't build with the emacs20 package i have installed. > > > > > > > > Is there a way of specifying that only xemacs installs should build a > > > > given .el or something such ? > > > > > > Yes, check the Emacs policy doc. The install scripts get passed the > flavor > > > (emacs20, emacs21, xemacs21) as the first argument, so the script can > check it > > > and skip it unless the flavor is xemacs21. You can download my > aplus-fsf-el > > > package source if you want an example. It only works with xemacs21, and > I > > > have both xemacs21 and emacs21 installed on my machines, so I know it's > > > working properly :-) > > > > > > > Ok, nice. Will the install script be called for every .el file, or only > > for the whole directory. I have a bunch of .el files, and only one has > > this problem. > > > > I will go read the emacs policy now, i guess it has the answer ... Now, > > there don't seem to be made any mention of this. > > The install script gets called once for each flavor, and since you write that, > you have total control over what it does. If foo.el is your xemacs specific > script, then some test like > > for f in *.el; do > if [ "$f" != "foo.el" ] || [ "$FLAVOR" != "xemacs" ] > ... > done > > should do it.
Ok, thanks, i will do it then. > [ No need to CC me, I'm on the list. ] Then set your mail-followup-to or somethign such header correctly ? Friendly, Sven Luther
