Port details |
- py-lml Load me later, a lazy plugin management system
- 0.1.0_1 devel
=2 0.1.0_1Version of this port present on the latest quarterly branch. - Maintainer: sunpoet@FreeBSD.org
 - Port Added: 2021-06-10 14:48:47
- Last Update: 2024-04-08 20:17:10
- Commit Hash: cc212a3
- People watching this port, also watch:: jdictionary, py311-Automat, py311-python-gdsii, py39-PyOpenGL, p5-Sane
- Also Listed In: python
- License: BSD3CLAUSE
- WWW:
- https://github.com/python-lml/lml
- Description:
- lml seamlessly finds the lml based plugins from your current python environment
but loads your plugins on demand. It is designed to support plugins that have
external dependencies, especially bulky and/or memory hungry ones. lml provides
the plugin management system only and the plugin interface is on your shoulder.
lml enabled applications helps your customers in two ways:
- Your customers could cherry-pick the plugins from pypi per python environment.
They could remove a plugin using pip uninstall command.
- Only the plugins used at runtime gets loaded into computer memory.
When you would use lml to refactor your existing code, it aims to flatten the
complexity and to shrink the size of your bulky python library by distributing
the similar functionalities across its plugins. However, you as the developer
need to do the code refactoring by yourself and lml would lend you a hand.
¦ ¦ ¦ ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - There is no configure plist information for this port.
- Dependency lines:
-
- ${PYTHON_PKGNAMEPREFIX}lml>0:devel/py-lml@${PY_FLAVOR}
- To install the port:
- cd /usr/ports/devel/py-lml/ && make install clean
- To add the package, run one of these commands:
- pkg install devel/py-lml
- pkg install py39-lml
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above. NOTE: This is a Python port. Instead of py39-lml listed in the above command, you can pick from the names under the Packages section.- PKGNAME: py39-lml
- Package flavors (<flavor>: <package>)
- distinfo:
- TIMESTAMP = 1622213918
SHA256 (lml-0.1.0.tar.gz) = 57a085a29bb7991d70d41c6c3144c560a8e35b4c1030ffb36d85fa058773bcc5
SIZE (lml-0.1.0.tar.gz) = 42010
Packages (timestamps in pop-ups are UTC):
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- py39-setuptools>=0 : devel/py-setuptools@py39
- py39-wheel>=0 : devel/py-wheel@py39
- python3.9 : lang/python39
- py39-build>=0 : devel/py-build@py39
- py39-installer>=0 : devel/py-installer@py39
- Test dependencies:
-
- python3.9 : lang/python39
- Runtime dependencies:
-
- python3.9 : lang/python39
- This port is required by:
- for Run
-
- textproc/py-pyexcel
- textproc/py-pyexcel-io
Configuration Options:
- No options to configure
- Options name:
- devel_py-lml
- USES:
- python
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
Number of commits found: 7
Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
Commit | Credits | Log message |
0.1.0_1 08 Apr 2024 20:17:10
    |
Po-Chuan Hsieh (sunpoet)  |
devel/py-lml: Convert to USE_PYTHON=pep517
- Bump PORTREVISION for package change |
0.1.0 27 Jun 2023 19:34:34
    |
Rene Ladan (rene)  |
all: remove explicit versions in USES=python for "3.x+"
The logic in USES=python will automatically convert this to 3.8+ by
itself.
Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.
finance/quickfix: mark BROKEN with PYTHON
libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++
-DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable
-Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong
-fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi
-Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings
-Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x
-MT _quickfix_la-QuickfixPython.lo -MD -MP -MF
.deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp -fPIC -DPIC -o
.libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
'-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
^~~~~~~~~~
1 warning and 1 error generated.
Reviewed by: portmgr, vishwin, yuri
Differential Revision: <https://reviews.freebsd.org/D40568> |
0.1.0 11 Jan 2023 15:58:34
    |
Dmitry Marakasov (amdmi3)  |
*/*: rename CHEESESHOP to PYPI in MASTER_SITES
PR: 267994
Differential revision: D37518
Approved by: bapt |
07 Sep 2022 21:58:51
    |
Stefan Eßer (se)  |
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) |
0.1.0 07 Sep 2022 21:10:59
    |
Stefan Eßer (se)  |
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 ) |
0.1.0 20 Jul 2022 14:21:35
    |
Tobias C. Berner (tcberner)  |
devel: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
* "Waitman Gobble" <uzimac@da3m0n8t3r.com>
* <jkoshy@FreeBSD.org>
* Aaron Dalton <aaron@FreeBSD.org>
* Aaron Dalton <aaron@daltons.ca>
* Aaron H. K. Diep <ahkdiep@gmail.com>
* Aaron Hurt <ahurt@anbcs.com>
* Abel Chow <abel_chow@yahoo.com>
* Adam McLaurin
* Adam Saponara <as@php.net>
* Adam Weinberger <adamw@FreeBSD.org>
* Ade Lovett <ade@FreeBSD.org> (Only the first 15 lines of the commit message are shown above ) |
0.1.0 10 Jun 2021 14:45:56
    |
Po-Chuan Hsieh (sunpoet)  |
devel/py-lml: Add py-lml 0.1.0
lml seamlessly finds the lml based plugins from your current python environment
but loads your plugins on demand. It is designed to support plugins that have
external dependencies, especially bulky and/or memory hungry ones. lml provides
the plugin management system only and the plugin interface is on your shoulder.
lml enabled applications helps your customers in two ways:
- Your customers could cherry-pick the plugins from pypi per python environment.
They could remove a plugin using pip uninstall command.
- Only the plugins used at runtime gets loaded into computer memory.
When you would use lml to refactor your existing code, it aims to flatten the
complexity and to shrink the size of your bulky python library by distributing
the similar functionalities across its plugins. However, you as the developer
need to do the code refactoring by yourself and lml would lend you a hand.
WWW: https://github.com/python-lml/lml |
Number of commits found: 7
|