[Bug 181404] Review Request: emacs-muse

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: emacs-muse


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=181404





------- Additional Comments From tagoh@xxxxxxxxxx  2006-04-25 07:52 EST -------
Well, I'm not blaming you on your packaging process. I'm sorry if you feel that way.

I mean you could just package your elisp as noarch package, and there shouldn't
be any different between architectures. if that's a problem, possibly it should
appears at the build time for a flavor of that emacsen. so I suppose you can
assume that the installation on all archs should be ok if you can install your
elisp successfully on your box. or is this wrong assumption?

Well, I'm not sure if I understood correctly your comment on elisp api though,
for instance, if your package, foo is updated, emacsen-common is just going to
byte-compile foo only, or another one if your install script invokes one -
actually in Debian, apel install script invokes flim install script so that it
depends on flim and sometimes broke without re-byte-compiling it, but anyway -
for all flavors of emacsen since the byte-compiled elisp files for foo is
out-of-date. and if only xemacs package is updated, emacsen-common is going to
remove all byte-compiled files for xemacs and byte-compile all elisp packages
for xemacs again. it won't touch other flavors of emacsen. so I'm not sure
what's "irrespective".

for good example above apel install script, here is quote:
  # recompile flim
  pkg=flim
  if [ -d /usr/share/${FLAVOR}/site-lisp/${pkg} ]; then
    if [ -f /usr/lib/emacsen-common/packages/install/${pkg} ]: then
      /usr/lib/emacsen-common/packages/remove/${pkg} ${FLAVOR}
      /usr/lib/emacsen-common/packages/install/${pkg} ${FLAVOR}
    fi
  fi

Those is what described in apel install script that put as
/usr/lib/emacsen-common/packages/install/apel on the debian box. and ${FLAVOR}
is to know which flavors of emacsen - including versions of emacsen - such as
emacs21 and xemacs21 install script is going to be invoked for.

Is it clear?

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

-- 
fedora-extras-list mailing list
fedora-extras-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-extras-list

[Index of Archives]     [Fedora General Discussion]     [Fedora Art]     [Fedora Docs]     [Fedora Package Review]     [Fedora Desktop]     [Big List of Linux Books]     [Yosemite Backpacking]     [KDE Users]

  Powered by Linux