From nobody Sat Mar 09 14:09:48 2024 X-Original-To: dev-commits-ports-all@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TsQ0D6PzLz5DFCh; Sat, 9 Mar 2024 14:09:48 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TsQ0D3vvGz4pCG; Sat, 9 Mar 2024 14:09:48 +0000 (UTC) (envelope-from git@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1709993388; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=NVMNElhOhu9OJzv5hr/195x/Sa/ZqEhPjNwtl+X1PUU=; b=wEJEz+yC1GuKoOZqRSE4CVOc4yXg8Hf6OdTZkvProrzUamvYMnVK971u3BUfHkrz/6osYP GoKQadWyoATB+H9JQuf+oGrwGImIUiTKuiCfaK91Bz+UJAGpwCvsREDBvb67yR6zl/UDRa AarWoVwb8w/CEYZmnBMbUhfoR4fec33/GWeo7jRr4f0S3QkwDHuCK6fDLE/rMx/YWJPkei jeVjkSasIJUAaTTjoNhf/veS0B0HG9j+IpGpCvnBaA995z3tVU8dk8I5J7uuWz2zxLX7Fg NrGdQKVoB0+sMHFpXbWqyHdS6o0mv1TPzhiuJ91Ca1VvX+q6jq8MI8mUPQiXnA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1709993388; a=rsa-sha256; cv=none; b=kVMJnIHOyA8GkmjGnAHXQaLBf9gOV76izqGknPjgfbilHb0Xlxbq101oPOY7lv0eOiwpXQ hGRcM8rmr2u/WoEoba1wbctA0hBbYntULWtPOEORtfc/zpf7J+U9YdCEyOVhy74RG02LF0 5EG1sSkXhSD1yg6iHxDttQNXJ7ZjglRZv/AkKEY/LBKWMdZCpZWnnTGT9A1LhKiG6S3+NZ pHSxJFD7uh4t0Qzb4pAF8NNxxzAK9reTgDiAVBd7ea/BtEWploYv9rp27j/l6KVcBADCUv JNBs9onpTcVDmIEtzMy7SiPkFWpc63MYO1q+nvcdhUmibYgn9fPgfTcskMz4Gg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1709993388; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=NVMNElhOhu9OJzv5hr/195x/Sa/ZqEhPjNwtl+X1PUU=; b=iG815E7oUjQsnPvrcw86ahQi0zOvwCAh+iKEqzqeZ2fvilztEU/v/RMwTjkP72kzBWrWus ki+jRq1qJ8ZyrvER13ctPQoJt2NEcCP1CEp3nq7T9t5IfdkYRM8wjG1TCOxcVmVbt3fdrN B6fnNAZhZMXMbv/j3hqacGbueLPN45ZMmSEPDi3f7oNF+mXH5JPj1/4421v2+Z6fRz64xN w6O/iS4sbAOJ7jHShMO3PNymkU5k3NYdjKmkmP+5PcMaTgF91ttbab4rJxntBwBuJNSmPa VdrJebHx3hMGdcgFwMsDl5Y9LxWkrw7DtMblRmXA9BEi3R0Kk8P51EqTnXV9+Q== Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4TsQ0D3WV6z14rG; Sat, 9 Mar 2024 14:09:48 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.17.1/8.17.1) with ESMTP id 429E9mv4093303; Sat, 9 Mar 2024 14:09:48 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.17.1/8.17.1/Submit) id 429E9mhx093300; Sat, 9 Mar 2024 14:09:48 GMT (envelope-from git) Date: Sat, 9 Mar 2024 14:09:48 GMT Message-Id: <202403091409.429E9mhx093300@gitrepo.freebsd.org> To: ports-committers@FreeBSD.org, dev-commits-ports-all@FreeBSD.org, dev-commits-ports-main@FreeBSD.org From: Po-Chuan Hsieh Subject: git: 4f4fc4eb07b0 - main - www/py-laces: Add py-laces 0.1.1 List-Id: Commit messages for all branches of the ports repository List-Archive: https://lists.freebsd.org/archives/dev-commits-ports-all List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-dev-commits-ports-all@freebsd.org X-BeenThere: dev-commits-ports-all@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: sunpoet X-Git-Repository: ports X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 4f4fc4eb07b05fccc08fd4b82e4fefc50ed94924 Auto-Submitted: auto-generated The branch main has been updated by sunpoet: URL: https://cgit.FreeBSD.org/ports/commit/?id=4f4fc4eb07b05fccc08fd4b82e4fefc50ed94924 commit 4f4fc4eb07b05fccc08fd4b82e4fefc50ed94924 Author: Po-Chuan Hsieh AuthorDate: 2024-03-09 13:44:33 +0000 Commit: Po-Chuan Hsieh CommitDate: 2024-03-09 14:05:16 +0000 www/py-laces: Add py-laces 0.1.1 Laces components provide a simple way to combine data (in the form of Python objects) with the Django templates that are meant to render that data. The components can then be simply rendered in any other template using the {% component %} template tag. That parent template does not need to know anything about the component's template or data. No need to receive, filter, restructure or pass any data to the component's template. Just let the component render itself. Template and data are tied together in the component, and they can be passed around together. This becomes especially useful when components are nested -- it allows us to avoid building the same nested structure twice (once in the data and again in the templates). Working with objects that know how to render themselves as HTML elements is a common pattern found in complex Django applications, such as the Wagtail admin interface. The Wagtail admin is also where the APIs provided in this package have previously been discovered, developed and solidified. The purpose of this package is to make these tools available to other Django projects outside the Wagtail ecosystem. --- www/Makefile | 1 + www/py-laces/Makefile | 23 +++++++++++++++++++++++ www/py-laces/distinfo | 3 +++ www/py-laces/pkg-descr | 19 +++++++++++++++++++ 4 files changed, 46 insertions(+) diff --git a/www/Makefile b/www/Makefile index 4e5fbc0d4bd3..bba5288de433 100644 --- a/www/Makefile +++ b/www/Makefile @@ -1754,6 +1754,7 @@ SUBDIR += py-jonpy SUBDIR += py-jsonfield SUBDIR += py-kiss-headers + SUBDIR += py-laces SUBDIR += py-lektor SUBDIR += py-lesscpy SUBDIR += py-libsass diff --git a/www/py-laces/Makefile b/www/py-laces/Makefile new file mode 100644 index 000000000000..5b44c4c908fc --- /dev/null +++ b/www/py-laces/Makefile @@ -0,0 +1,23 @@ +PORTNAME= laces +PORTVERSION= 0.1.1 +CATEGORIES= www python +MASTER_SITES= PYPI +PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX} + +MAINTAINER= sunpoet@FreeBSD.org +COMMENT= Django components that know how to render themselves +WWW= https://github.com/tbrlpld/laces + +LICENSE= BSD3CLAUSE +LICENSE_FILE= ${WRKSRC}/LICENSE + +BUILD_DEPENDS= ${PYTHON_PKGNAMEPREFIX}django42>=3.2:www/py-django42@${PY_FLAVOR} \ + ${PYTHON_PKGNAMEPREFIX}flit-core>=3.2<4:devel/py-flit-core@${PY_FLAVOR} +RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}django42>=3.2:www/py-django42@${PY_FLAVOR} + +USES= python +USE_PYTHON= autoplist concurrent pep517 + +NO_ARCH= yes + +.include diff --git a/www/py-laces/distinfo b/www/py-laces/distinfo new file mode 100644 index 000000000000..b5d48389d77a --- /dev/null +++ b/www/py-laces/distinfo @@ -0,0 +1,3 @@ +TIMESTAMP = 1709390340 +SHA256 (laces-0.1.1.tar.gz) = e45159c46f6adca33010d34e9af869e57201b70675c6dc088e919b16c89456a4 +SIZE (laces-0.1.1.tar.gz) = 26889 diff --git a/www/py-laces/pkg-descr b/www/py-laces/pkg-descr new file mode 100644 index 000000000000..92ed9f19a42e --- /dev/null +++ b/www/py-laces/pkg-descr @@ -0,0 +1,19 @@ +Laces components provide a simple way to combine data (in the form of Python +objects) with the Django templates that are meant to render that data. The +components can then be simply rendered in any other template using the {% +component %} template tag. That parent template does not need to know anything +about the component's template or data. No need to receive, filter, restructure +or pass any data to the component's template. Just let the component render +itself. + +Template and data are tied together in the component, and they can be passed +around together. This becomes especially useful when components are nested -- it +allows us to avoid building the same nested structure twice (once in the data +and again in the templates). + +Working with objects that know how to render themselves as HTML elements is a +common pattern found in complex Django applications, such as the Wagtail admin +interface. The Wagtail admin is also where the APIs provided in this package +have previously been discovered, developed and solidified. The purpose of this +package is to make these tools available to other Django projects outside the +Wagtail ecosystem.