From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Payas Relekar Newsgroups: gmane.emacs.devel Subject: [ELPA] New package: use-package Date: Tue, 25 Oct 2022 17:02:04 +0530 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000097207c05ebda42ef" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16202"; mail-complaints-to="usenet@ciao.gmane.io" Cc: John Wiegley To: emacs-devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Oct 25 13:43:13 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1onIKv-00044I-4s for ged-emacs-devel@m.gmane-mx.org; Tue, 25 Oct 2022 13:43:13 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1onIJU-0000rD-3l; Tue, 25 Oct 2022 07:41:44 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1onIAQ-00034U-91 for emacs-devel@gnu.org; Tue, 25 Oct 2022 07:32:22 -0400 Original-Received: from mail-wr1-x42f.google.com ([2a00:1450:4864:20::42f]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1onIAO-000628-CZ; Tue, 25 Oct 2022 07:32:21 -0400 Original-Received: by mail-wr1-x42f.google.com with SMTP id k8so11602110wrh.1; Tue, 25 Oct 2022 04:32:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=sVGKXByBzPElC1sRpeuqujNBIDnXG0WpSuRaLORDajE=; b=acFcxxybGIqRyxgMsrHK+5aEeVkJSimWv4/yEp1KsbUqr7v3peozTUVCUEFvPLlKVS Nex3wFcFVLr7EwTGtvPS96LKUX/KaA47kYHcnhbPgqbzjp9BkG8B7bSLeojLMakm5M+Q J/+9gh17iQCFVCssCM/RFdZZPXuysa3kKIwD5JnU0fS/4sOFPS87WXPY6zjWTXcV1/Vd E3XTSuSKoTSwnqXHSJqUpObSIVRslOeM5tG0+caqvUcNBfWSA062/HjLvnQRh6r4A4FI oQMT3m6BZmPc53APpkCIrmae78Oab3KgbWHt8nlg641v+zEZAUwdP779qZJMHApxB7CR +GjA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=sVGKXByBzPElC1sRpeuqujNBIDnXG0WpSuRaLORDajE=; b=X4XWA7RhzJctMAfPFE284ILZ8p7eGy5nygHhvogJzVK+BLBD+17Ch+7uWv+C4JS53X BThbEQDVIK5aftAs8zmJLigtF0/fhbCMBakK42tlF5Al85qLPuKv/ildgW56djh/LEC/ SrcOQfyptp5iFz6nhXlOECDRD0tTRVzwY2WtAApQ5m5EAOiCX0AeIrwQ0cYD46wwd2Nw bWVC1khPxtr9mp4KmMnYS2z5p7L5XJJ4boaByAv0hNYD9xMIZU7MUkLk2rhM6beGDS+E FW88/p3PfHPyv/s2wbayfYBPIVBLhgumfBrr0FKq9aOd8is4+PVMfn99fH7vWyf9sZan e+1A== X-Gm-Message-State: ACrzQf2Mjx3EBHuA1hm/ewCs4aGkDscXKMjldKpmt22kqicIFlXu66Js 2rlPKscShNjE8aqAGUu1Pmc2QXdqM8nYrZ/yWZ5jqXN+ X-Google-Smtp-Source: AMsMyM7NkReFME0myQkfmYexyt39HQs/fxuX/bUW8PzcyMp6oAGmMht/QZfBWQeAp6+LIiwXN26P2vIPKIxKxLFKUNo= X-Received: by 2002:a05:6000:1e03:b0:22e:3bf2:4685 with SMTP id bj3-20020a0560001e0300b0022e3bf24685mr24890022wrb.82.1666697536150; Tue, 25 Oct 2022 04:32:16 -0700 (PDT) Received-SPF: pass client-ip=2a00:1450:4864:20::42f; envelope-from=relekarpayas@gmail.com; helo=mail-wr1-x42f.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Tue, 25 Oct 2022 07:41:29 -0400 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: "Emacs-devel" Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:298454 Archived-At: --00000000000097207c05ebda42ef Content-Type: text/plain; charset="UTF-8" As per previous discussion, here is a patch to submit "use-package" to GNU ELPA. According to John Wiegley (cc'd) copyright assignment is done, so there should be nothing to stop getting use-package added to ELPA. Since John personally cannot commit time to undertake the janitorial work to do necessary changes and upstream it, I would like to carry out that task. However, considering my personal time and elisp skills, not to mention understanding of use-package codebase is less than perfect at the moment, it might take me a while, and definitely will not be completed before 29 branch-off. If someone else wants to pick up the pace, please feel free to take over. As for any changes necessary to get accepted to ELPA, please let me know. I have tried to go through ELPA manual and refer to MELPA recipe as well as few other packages already in ELPA package list, but it very possible to have missed something. I'm following these instructions, but since I don't have an account on ELPA, I'd like to ask how to proceed further. 1. Notify emacs-devel@gnu.org. 2. Push your package's code to its branch on elpa.git with: $ git push elpa :refs/heads/externals/ where == will probably be =master= for most people. [ Note: The name "externals/" is the result of an accident of history. ] 3. Edit the =elpa-packages= file to add an entry for ==. It has to have an =:url= property specified but that property can be nil. 4. =git add elpa-packages=, =git commit= and =git push=. If you don't have push access to the repository, someone will do steps 2-4 for you. Please be kind for any rookie mistakes, this is my first time contributing to a GNU project. Also, I do not have any copyright assignment papers signed, but I also do not have any changes in use-package or any GNU project just yet. Is it needed for ELPA patch? It is well under 15 lines, but I'd rather be safe. Thanks, Payas -- <#part type="text/x-patch" filename="~/git/elpa/0001-elpa-packages-use-package-New-package.patch" disposition=attachment> <#/part> --00000000000097207c05ebda42ef Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
As per previous discussion, here is a patch to submit &qu= ot;use-package" to
GNU ELPA.

According to John Wiegley (cc'd) copyright assignment is done, so there=
should be nothing to stop getting use-package added to ELPA.

Since John personally cannot commit time to undertake the janitorial
work to do necessary changes and upstream it, I would like to carry out
that task.
However, considering my personal time and elisp skills, not to mention
understanding of use-package codebase is less than perfect at the
moment, it might take me a while, and definitely will not be completed
before 29 branch-off. If someone else wants to pick up the pace, please
feel free to take over.

As for any changes necessary to get accepted to ELPA, please let me
know.

I have tried to go through ELPA manual and refer to MELPA recipe as well as few other packages already in ELPA package list, but it very possible to have missed something. I'm following these instructions, but since I=
don't have an account on ELPA, I'd like to ask how to proceed furth= er.

1. Notify emacs-devel@gnu.org.
2. Push your package's code to its branch on elpa.git with:

=C2=A0 =C2=A0$ git push elpa <mybranch>:refs/heads/externals/<pkgn= ame>

=C2=A0 =C2=A0where =3D<mybranch>=3D will probably be =3Dmaster=3D for= most people.
=C2=A0 =C2=A0[ Note: The name "externals/" is the result of an ac= cident of history.=C2=A0 ]

3. Edit the =3Delpa-packages=3D file to add an entry for =3D<pkgname>= =3D.
=C2=A0 =C2=A0It has to have an =3D:url=3D property specified but that
=C2=A0 =C2=A0property can be nil.
4. =3Dgit add elpa-packages=3D, =3Dgit commit=3D and =3Dgit push=3D.

If you don't have push access to the repository, someone will do steps<= br> 2-4 for you.

Please be kind for any rookie mistakes, this is my first time
contributing to a GNU project.

Also, I do not have any copyright assignment papers signed, but I also
do not have any changes in use-package or any GNU project just yet. Is
it needed for ELPA patch? It is well under 15 lines, but I'd rather be<= br> safe.

Thanks,
Payas

--
<#part type=3D"text/x-patch" filename=3D"~/git/elpa/0001-= elpa-packages-use-package-New-package.patch" disposition=3Dattachment&= gt;
<#/part>
--00000000000097207c05ebda42ef--