From: phillip.lord@newcastle.ac.uk (Phillip Lord)
To: Nic Ferrier <nferrier@ferrier.me.uk>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: package and testing rant (was Re: package.el, auto-installation, and auto-removal)
Date: Tue, 11 Nov 2014 13:30:46 +0000 [thread overview]
Message-ID: <87y4rhuant.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <87k332lnn3.fsf_-_@ferrier.me.uk> (Nic Ferrier's message of "Mon, 10 Nov 2014 22:02:56 +0000")
Nic Ferrier <nferrier@ferrier.me.uk> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>> I am still cross about the whole state of packaging. It's wrong. But no
>>> one seems to be listening to me.
>>
>> I'm not sure if you're referring to the way GNU ELPA works or about
>> package.el. About GNU ELPA, it's not that I don't listen, but that
>> I disagree. The point of GNU ELPA to not to just distribute other
>> people's packages.
>
> The multi-packages users load in their emacs are tars. But the packages
> that are checked in to ELPA are directories of files.
>
> So package authors are not checking in what gets delivered to the
> user. So there is a magic build step somewhere.
It is certainly the case that I most "test" my packages by using them.
And I do not install my own packages through ELPA but live from their
VC'd repository. So, there is a worry here. This is even true during my
continuous integration tests (the dependencies are loaded from an ELPA
repo, but nothing else).
Having said that, I generally use an automatic tool to move from the
source repository format to the package format; or, in the case of
MELPA, someone else does it for me. Once this is set up, I am struggling
to think of bugs that have come at package time.
> This discourages testing of packages before they are distributed.
>
> And I am really starting to think we need better testing. 24.4 looked
> like a slog to release and it still has many bugs.
>
> And yes, I promise to help more. But that's not really the issue. This
> isn't scaling. We need to have better QA tools. And packages having
> hidden builds is going the other way.
Not going to argue here. Slowing moving my elisp to a testable state has
made me happier.
Phil
next prev parent reply other threads:[~2014-11-11 13:30 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 13:45 package.el, auto-installation, and auto-removal Stefan Monnier
2014-11-07 14:12 ` Ted Zlatanov
2014-11-07 19:50 ` joakim
2014-11-08 4:27 ` Stefan Monnier
2014-11-10 14:55 ` Phillip Lord
2014-11-10 17:46 ` Ted Zlatanov
2014-11-10 20:27 ` Nic Ferrier
2014-11-10 21:49 ` Stefan Monnier
2014-11-10 22:02 ` package and testing rant (was Re: package.el, auto-installation, and auto-removal) Nic Ferrier
2014-11-10 23:24 ` Stefan Monnier
2014-11-11 2:53 ` Drew Adams
2014-11-11 11:41 ` Nic Ferrier
2014-11-11 16:03 ` Eli Zaretskii
2014-11-11 17:17 ` Nic Ferrier
2014-11-11 17:20 ` Stefan Monnier
2014-11-11 17:53 ` Eli Zaretskii
2014-11-11 16:24 ` Stefan Monnier
2014-11-11 17:15 ` Nic Ferrier
2014-11-11 15:57 ` Eli Zaretskii
2014-11-11 17:18 ` Stefan Monnier
2014-11-11 17:52 ` Eli Zaretskii
2014-11-11 18:04 ` David Kastrup
2014-11-12 3:20 ` Stephen J. Turnbull
2014-11-12 6:48 ` David Kastrup
2014-11-11 17:27 ` Nic Ferrier
2014-11-11 18:20 ` Achim Gratz
2014-11-12 16:13 ` Stefan Monnier
2014-11-12 17:00 ` Stephen Leake
2014-11-12 17:51 ` Nic Ferrier
2014-11-12 20:34 ` Stefan Monnier
2014-11-12 21:39 ` Nic Ferrier
2014-11-12 22:40 ` Stefan Monnier
2014-11-12 23:01 ` Nic Ferrier
2014-11-12 23:31 ` Stefan Monnier
2014-11-13 1:09 ` Stephen J. Turnbull
2014-11-13 5:06 ` Richard Stallman
2014-11-13 14:59 ` Nic Ferrier
2014-11-15 17:09 ` Stephen Leake
2014-11-15 18:20 ` Nic Ferrier
2014-11-16 3:49 ` Stefan Monnier
2014-11-13 8:18 ` Thien-Thi Nguyen
2014-11-13 10:53 ` Phillip Lord
2014-11-13 14:54 ` Nic Ferrier
2014-11-14 11:04 ` Phillip Lord
2014-11-14 22:56 ` Nic Ferrier
2014-11-12 18:15 ` Achim Gratz
2014-11-12 22:21 ` Stefan Monnier
2014-11-13 20:21 ` Achim Gratz
2014-11-12 13:05 ` Stephen Leake
2014-11-11 13:30 ` Phillip Lord [this message]
2014-11-11 14:12 ` Nic Ferrier
2014-11-11 16:26 ` Stefan Monnier
2014-11-11 17:13 ` Nic Ferrier
2014-11-12 16:14 ` Stefan Monnier
2014-11-12 17:02 ` Stephen Leake
2014-11-12 17:21 ` Stefan Monnier
2014-11-10 21:37 ` package.el, auto-installation, and auto-removal Stefan Monnier
2014-11-11 1:29 ` Ted Zlatanov
2014-11-11 2:26 ` Stefan Monnier
2014-11-11 2:59 ` Ted Zlatanov
2014-11-11 3:55 ` Stefan Monnier
2014-11-11 12:44 ` Phillip Lord
2014-11-11 13:31 ` Nic Ferrier
2014-11-11 11:31 ` Nic Ferrier
2014-11-11 16:22 ` Stefan Monnier
2014-11-11 17:10 ` Nic Ferrier
2014-11-11 19:36 ` Achim Gratz
2014-11-11 20:40 ` Nic Ferrier
2014-11-11 21:53 ` Stefan Monnier
2014-11-12 22:17 ` Nic Ferrier
2014-11-12 22:59 ` Stefan Monnier
2014-11-12 23:26 ` Nic Ferrier
2014-11-13 0:21 ` Stefan Monnier
2014-11-07 20:00 ` Nic Ferrier
2014-11-08 4:29 ` Stefan Monnier
2014-11-08 23:18 ` Nic Ferrier
2014-11-09 3:17 ` Stefan Monnier
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=87y4rhuant.fsf@newcastle.ac.uk \
--to=phillip.lord@newcastle.ac.uk \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=nferrier@ferrier.me.uk \
/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).