Upstream is moving the bbdb project repo from nongnu.org to ELPA-gnu
which makes it official gnu.org. Or something like that. And so it
seems like a good time to move the debian packaging repo from
https://salsa.debian.org/debian/bbdb3.git to
https://salsa.debian.org/emacsen-team/bbdb3.git, and lis
To my mind, the natural solution is to put git-commit.el in elpa-magit
(as upstream wants) but keep the elpa-git-commit package around,
empty, and with a Depends: elpa-magit (>= xxx) or even Depends:
elpa-magit (== xxx) to ensure that git-commit.el is pulled in. And
elpa-magit has a Breaks: elpa-gi
; mfv
>
>
> Il dom 3 nov 2024, 09:04 Barak A. Pearlmutter ha scritto:
>>
>> True: transient needs to be uploaded too.
>>
>> I tested locally with my own updated transient. But I actually hadn't
>> finished testing; there's an issue where the test suit
True: transient needs to be uploaded too.
I tested locally with my own updated transient. But I actually hadn't
finished testing; there's an issue where the test suite runs okay in the CI
systems (minimal install) but gets a failure running an emacsclient and
blocking on wait for the recursive edi
I pushed a quick update, it has a few test failures though.
Package: elpa-use-package
Version: 2.4.4-1
I am a fun-loving bloke so /usr/games is on my path and pacman (the
package) is installed. When emacs is started and elpa-use-package
loads and searches for an appropriate value for
system-packages-package-manager it finds the executable
/usr/games/pacman
I've no objections to moving the repo to emacsen-team/. And please, go
ahead and give it some love! I've been too busy writing Haskell using
haskell-mode to test a new version.
Thanks for the note.
Don't worry, Lev is already on top of the situation, and has an
appropriate -2 release already pushed to git.
If you folks want to move the git repo, I'm happy to. The only reason
I didn't earlier is that the repo it was in pre-dated the elpa-
packaging stuff. Maybe they can
> For starters maybe you could add some ideas to the policy-in-progress on
> the wiki; it's an ikiwiki instance, so just
>
>git clone git.debian.org:/git/pkg-emacsen/wiki
>
> and push back when you're done.
Good idea.
I added some example snippets to the wiki.
The hooks were slightly annoyed w
> But how do I get the auto-mode-alist tweaked to made this the default
> mode for .vala files?
This would be an issue for the elpa-markdown-mode package as well, I think.
Perhaps this is something that could be addressed by putting some fields
into the debian/*.elpa file, maybe something like
I'm converting my most trivial emacs package, vala-mode-el, to
elpa-vala-mode. In vala-mode-el, the emacsen-startup file contains this
snippet:
(autoload 'vala-mode "vala-mode" "Major mode for editing Vala code." t)
(add-to-list 'auto-mode-alist '("\\.vala$" . vala-mode))
(add-to-list
That sounds fine to me.
It would also allow some "workhorse" scripts so, in most cases,
packages could just
go
elfiles=foo.el bar.el autoload.el
. /usr/lib/emacsen-common/emacs-install-standard.sh
which has a lot of advantages.
Cheers,
--Barak.
--
To UNSUBSCRIBE, email to debian-emacse
12 matches
Mail list logo
