From: Jean Louis <bugs@gnu.support>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Arthur Miller <arthur.miller@live.com>, emacs-devel@gnu.org
Subject: Packages for ELPA, emacs-libpq
Date: Sat, 3 Apr 2021 19:26:50 +0300 [thread overview]
Message-ID: <YGiXSkO6H0wep8He@protected.localdomain> (raw)
In-Reply-To: <jwv5z13zda4.fsf-monnier+emacs@gnu.org>
Dear Stefan,
* Stefan Monnier <monnier@iro.umontreal.ca> [2021-04-03 16:55]:
> > Personally I do not need version numbers, but Emacs package needs
> > it. Presentation as floating point is I think, but not so sure, one
> > of possibilities.
> >
> > My function is not quite compatible with `version-to-list'.
>
> I haven't followed what you're doing (so I have no idea if your "Emacs
> packages" are ELPA packages), but I'll point out that ELPA package
> version numbers *have to* be compatible with `version-to-list`.
Discussion is about one package I am using personally for version
control. Its requirement is package `emacs-libpq'. Once `emacs-libpq'
is in ELPA, there will be new packages for ELPA based on it.
This package that I use now is `rcd-vc' that provides version control
based on database backend. I find it naive yet, but it works for my
personal needs. It will improve. People may use any kinds of version
control names or numbers and not only for Emacs Lisp.
I am moving this email to emacs-devel, from gnu-hhelp-emacs
emacs-libpq is package that should come to ELPA, authors have already
agreed on it, I think they would need help from developers, some
assistance on how to provide package to ELPA. It is very significant
package as it provides module for PostgreSQL database.
Link: https://github.com/anse1/emacs-libpq
Please see the issue:
https://github.com/anse1/emacs-libpq/issues/12
They agreed. Recently before few months, they wrote on the mailing
list. Both of them said to have sent copyright assignments. Can you
verify it?
Can you help that package get included?
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
Sign an open letter in support of Richard M. Stallman
https://rms-support-letter.github.io/
next prev parent reply other threads:[~2021-04-03 16:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 13:42 What is 0.01 here not 0.01 here 0.009999999999999? Jean Louis
2021-04-02 13:56 ` Stefan Monnier
2021-04-02 17:03 ` Jean Louis
2021-04-02 17:41 ` Teemu Likonen
2021-04-02 18:44 ` Jean Louis
2021-04-02 20:46 ` John Yates
2021-04-02 21:19 ` Jean Louis
2021-04-02 22:04 ` John Yates
2021-04-02 23:29 ` Jean Louis
2021-04-03 4:39 ` Arthur Miller
2021-04-03 5:36 ` Jean Louis
2021-04-03 3:56 ` Arthur Miller
2021-04-03 5:19 ` Jean Louis
2021-04-03 13:54 ` Stefan Monnier
2021-04-03 16:26 ` Jean Louis [this message]
2021-04-02 14:02 ` Eli Zaretskii
2021-04-02 17:07 ` Jean Louis
2021-04-03 4:49 ` Arthur Miller
2021-04-16 20:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-04-17 10:53 ` Jean Louis
2021-04-19 10:51 ` Eric S Fraga
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YGiXSkO6H0wep8He@protected.localdomain \
--to=bugs@gnu.support \
--cc=arthur.miller@live.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.