Ghub is a library that provides basic support for using the Github
REST (v3) and GraphQL (v4) APIs from Emacs packages. It abstracts
access to API resources using only a handful of functions that are not
resource-specific.
Ghub handles the creation, storage and use of access tokens using a
setup wizard to make it easier for users to get started and to reduce
the support burden imposed on package maintainers. It also comes with
a comprehensive manual to address the cases when things don't just
work as expected or in case you don't want to use the wizard.
Ghub is intentionally limited to only provide these two essential
features - basic request functions and guided setup - to avoid being
too opinionated, which would hinder wide adoption. It is assumed that
wide adoption would make life easier for users and maintainers alike,
because then all packages that talk to the Github API could be
configured the same way.
===> The following configuration options are available for ghub-devel-4.3.2_1:
DOCS=on: Build and/or install documentation
PDF=off: Build and install PDF document
===> Use 'make config' to modify these settings
Magit: Mark development snapshot ports as DEPRECATED and set EXPIRATION_DATE
After Magit 3.3.0 was released on October 2021, upstream didn't
release new version for a long time. So I created development snapshot
ports to used newer Magit. But they seems to change release policy
with the release of 4.0.0 on August 2024, and new versions have been
released every month since then. Since I have updated development
snapshot ports once a month, there aren't much difference from release
version ones now. So mark the former as DEPRECATED and set
EXPIRATION_DATE.
Chase major version update of editors/emacs-devel
Bump PORTREVISION of most USES=emacs ports after editors/emacs-devel
major version increased from 30 to 31.
Sponsored by: The FreeBSD Foundation
Chase editors/emacs update to 29.4
- Bump Emacs version in Mk/Uses/emacs.mk to update version-specific
paths
- Bump PORTREVISION of ports with USES=emacs. This is required for two
reasons. Emacs lisp files need to be byte compiled for the new Emacs
version, and files installed under, e.g., EMACS_VERSION_SITE_LISPDIR
need to be relocated.
Reviewed by: ashish, yasu
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D45705
*/*: Fix build when PDF option is enabled
When PDF option is enabled PDF file is generated from Texinfo source
file with texi2pdf, and the command is invoked with '--clear'
option. When the command is invoked with the option, however, it
returns non-zero value even if conversion is (or, at least seems to
be) successful. As a result build of ports fails when the option is
enabled. The command returns zero value if it is invoked without the
option. So fix build by patching Makefile of source tree.
While I'm here, replace CONFLICTS in devel/{forge,forge-devel/Makefile
with CONFLICTS_INSTALL as neither of them interfere with build of the
other.
Chase editors/emacs update
- Bump Emacs version in Mk/Uses/emacs.mk to update version-specific
paths
- Bump PORTREVISION of ports with USES=emacs. This is required for two
reasons. Emacs lisp files need to be byte compiled for the new Emacs
version, and files installed under, e.g., EMACS_VERSION_SITE_LISPDIR
need to be relocated.
Reviewed by: ashish
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D44492
*/*: Chase editors/emacs update
- Bump Emacs version in Mk/Uses/emacs.mk to update version-specific
paths
- Bump PORTREVISION of ports with USES=emacs. This is required for two
reasons. Emacs lisp files need to be byte compiled for the new Emacs
version, and files installed under, e.g., EMACS_VERSION_SITE_LISPDIR
need to be relocated.
Reviewed by: ashish
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D43615
editors/emacs: Update to 29.1
* Update Canna patch to the one for Emacs 29.
* Add new options PGTK, SQLITE3, TREESITTER and WEBP. SQLITE3 and
TREESITTER are ON by default. PGTK and WEBP options are excluded
from nox flavor.
* CARGO option doesn't imply XFT but prevents it. It is caused as a
result of adding pure GTK support (PGTK option).
* OTK options doesn't imply XTF any more. It is also caused as a
result of adding pure GTK support.
* Update NATIVECOMP option so it specifies ahead-of-time compilation
via the configure argument.
* Remove "experimental" from NATIVECOMP_DESC.
* Add print/freetype2 and x11-fonts/fontconfig to CAIRO_LIB_DEPENDS
and GTK3_LIB_DEPENDS. Necessary to link emacs binary with shared
(Only the first 15 lines of the commit message are shown above )
Mk/**tex.mk: Convert bsd.tex.mk to USES=tex
- Update all the consumers to use USES=tex
- USE_TEX=yes is the old way of writing USES=tex which has been removed
and replaced in all ports
- Almost all of the USE_TEX features remains unchanged
- Some consumers had the same variables defined both in the mk
infrastructure and also in the ports which have been removed from the
ports as those are redundant.
In case any of the consumers are failing to build please make sure that
the nexessary USES=tex is there. Unlike previous USE_TEX=yes will no
longer load the required VARS for tex and related dependencies.
Reviewed by: portmgr
Approved by: portmgr (blanket)
devel/ghub-devel: Mark MAKE_JOBS_UNSAFE
I have been receiving build error of this port from pkg-fallout. I
myself can't reproduce it. But I experienced similar problem with
devel/magit-devel and devel/forge-devel before and it was fixed by
disabling parallel build. So mark MAKE_JOBS_UNSAFE hoping it also
fixes build error of this port. At least it doesn't make things worse.
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
devel/ghub-devel: Add new port
Add devel/ghub-devel, development version of client libraries for the
APIs of various Git forges.
https://github.com/magit/ghub
