unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: "Amar M. Singh" <nly@disroot.org>
Cc: 38746@debbugs.gnu.org, Brett Gilio <brettg@gnu.org>
Subject: [bug#38746] [PATCH] gnu: emacs-shroud: Update to 1.105.
Date: Thu, 26 Dec 2019 08:30:00 +0200	[thread overview]
Message-ID: <20191226063000.GG23018@E5400> (raw)
In-Reply-To: <C661163A-AB7A-4434-B91E-6B89CC404B52@disroot.org>

[-- Attachment #1: Type: text/plain, Size: 2689 bytes --]

On Thu, Dec 26, 2019 at 03:58:19AM +0000, Amar M. Singh wrote:
> 
> Dec 25, 2019 9:42:15 PM Amar M. Singh :
> 
> >
> > New in this release:
> > 1. Now uses Gnu build system, aka Autotools.
> > 2. Comes with Texinfo documentation.
> >
> 
> Hi Amar,
> 
> I am looking at this on my phone, so I might be wrong but it looks like the change to the gnu-build-system is not accompanied by any arguments installing any byte-compiled elc files to the emacs site-lisp. Did you test this change? Are the elc files getting installed? If so, how? Normally we have to work around this issue with mixing gnu and Emacs build system phases. Also, things like autoconf and automake are implicit in the gnu build system and are not needed.
> 

tree /gnu/store/0m5irk4q5hf3pw2ral0gv9y51qic7m9x-emacs-shroud-1.83.4
/gnu/store/0m5irk4q5hf3pw2ral0gv9y51qic7m9x-emacs-shroud-1.83.4
└── share
    ├── doc
    │   └── emacs-shroud-1.83.4
    │       └── COPYING
    └── emacs
        └── site-lisp
            ├── shroud-autoloads.el
            ├── shroud-bui.el
            ├── shroud-bui.elc
            ├── shroud-cli.el
            ├── shroud-cli.elc
            ├── shroud.el
            ├── shroud.elc
            ├── shroud-el.el
            └── shroud-el.elc

tree /gnu/store/j0wmnl8gyzf4qwpxlml7hlvqpdzsw7p6-emacs-shroud-1.105
/gnu/store/j0wmnl8gyzf4qwpxlml7hlvqpdzsw7p6-emacs-shroud-1.105
└── share
    ├── doc
    │   ├── emacs-shroud
    │   │   ├── emacs-shroud.html
    │   │   └── README
    │   └── emacs-shroud-1.105
    │       └── COPYING
    ├── emacs
    │   └── site-lisp
    │       ├── shroud-bui.el
    │       ├── shroud-bui.elc
    │       ├── shroud-cli.el
    │       ├── shroud-cli.elc
    │       ├── shroud.el
    │       ├── shroud.elc
    │       ├── shroud-el.el
    │       └── shroud-el.elc
    └── info
        └── emacs-shroud.info.gz

> 
> Hi Brett,
> 
> I am using autoconf macro 'dist_lisp_LISP' in src/Makefile.am which will install '.el' files. Autotools are automatically detecting and installing '.elc' files from 'lisp_LISP' variable.
> 

I'm not an emacs user, do we need shroud-autoloads.el to be installed
also?

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-12-26  6:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-26  3:40 [bug#38746] [PATCH] gnu: emacs-shroud: Update to 1.105 Amar M. Singh
2019-12-26  3:51 ` Brett Gilio
2019-12-26  3:58   ` Amar M. Singh
2019-12-26  6:30     ` Efraim Flashner [this message]
2019-12-26 13:49       ` Amar M. Singh
2019-12-28 19:40         ` bug#38746: " Efraim Flashner
2019-12-28 21:34           ` [bug#38746] " Amar M. Singh

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191226063000.GG23018@E5400 \
    --to=efraim@flashner.co.il \
    --cc=38746@debbugs.gnu.org \
    --cc=brettg@gnu.org \
    --cc=nly@disroot.org \
    /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/guix.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).