> On Nov 10, 2023, at 11:24, BERTHAULT Justin
> wrote:
>
> Hi,
>
> Simple update to pelican 4.8.0
Thanks for taking care of it. I don't use this software anymore, would you mind
taking ownership?
--
David
On Wed, 2023-10-11 at 17:17 +, Chris Narkiewicz wrote:
> https://m.slashdot.org/story/420067
>
> TL;DR, the writing is on the wall, but I'm wondering how gnome port
> maintainers see this development? We already lost KDE. Are we in
> danger of losing Gnome as well?
At least general X11 suppor
> On 14 May 2022, at 03:43, Ryan Freeman wrote:
>
> Hello ports@,
>
> Here is an attempt to update retroarch to 1.10.3. Lots has changed, but
> it still works with the existing libretro-* core packages that I tested**.
Hi,
I wanted to work on it but it’s great that you did it before!
Howev
On Fri, 2022-05-06 at 00:31 +0200, Omar Polo wrote:
> I don't use pelican, but at glance there are three things to fix in
> the
> proposed diff:
>
> - remove REVISION: it's incremented every time a port is changed
> (security patches or changes to some fields like COMMENT or the
> descripti
GH_PROJECT = pelican
-GH_TAGNAME = 4.0.1
+GH_TAGNAME = 4.7.2
CATEGORIES = www
HOMEPAGE = https://blog.getpelican.com/
+MAINTAINER = David Demelier
# GPLv3
PERMIT_PACKAGE = Yes
@@ -20,6 +21,7 @@ MODPY_SETUPTOOLS = Yes
RUN_DEPENDS = devel/py-blinker${MODPY_FLAVOR} \
devel/py
