1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
|
[](https://github.com/gentoo/portage/actions/workflows/ci.yml)
About Portage
=============
Portage is a package management system based on ports collections. The
Package Manager Specification Project (PMS) standardises and documents
the behaviour of Portage so that ebuild repositories can be used by
other package managers.
Contributing
============
Contributions are always welcome! We've started using
[black](https://pypi.org/project/black/) to format the code base. Please make
sure you run it against any PR's prior to submitting (otherwise we'll probably
reject it).
There are [ways to
integrate](https://black.readthedocs.io/en/stable/integrations/editors.html)
black into your text editor and/or IDE.
You can also set up a git hook to check your commits, in case you don't want
editor integration. Something like this:
```sh
# .git/hooks/pre-commit (don't forget to chmod +x)
#!/bin/bash
black --check --diff .
```
One can also use pre-commit to run the configured pre-commit
hooks. Utilizing pre-commit has the advantage of running the linter
over only the changed files, resulting in a much faster pre-commit
hook. To use, install pre-commit and then install the hook to your
.git:
```sh
emerge dev-vcs/pre-commit
pre-commit install
```
To ignore commit 1bb64ff452 (and other reformatting commits) which is a
massive commit that simply formatted the code base using black - you can do
the following:
```sh
git config blame.ignoreRevsFile .git-blame-ignore-revs
```
Dependencies
============
Python and Bash should be the only hard dependencies. Python 3.9 is the
minimum supported version.
Native Extensions
=================
Portage includes some optional native extensions which can be built
in the source tree by running the following command:
python setup.py build_ext --inplace --portage-ext-modules
The following setup.cfg settings can be used to enable building of
native extensions for all invocations of the build_ext command (the
build_ext command is invoked automatically by other build commands):
```
[build_ext]
portage_ext_modules=true
```
Currently, the native extensions only include libc bindings which are
used to validate LC_CTYPE and LC_COLLATE behavior for EAPI 6. If the
native extensions have not been built, then portage will use ctypes
instead.
Licensing and Legalese
=======================
Portage is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
version 2 as published by the Free Software Foundation.
Portage is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with Portage; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
02110-1301, USA.
More information
================
- DEVELOPING contains some code guidelines.
- LICENSE contains the GNU General Public License version 2.
- NEWS contains new features/major bug fixes for each version.
- RELEASE NOTES contains mainly upgrade information for each version.
- TEST-NOTES contains Portage unit test information.
Links
=====
- Gentoo project page: https://wiki.gentoo.org/wiki/Project:Portage
- PMS: https://dev.gentoo.org/~ulm/pms/head/pms.html
- PMS git repo: https://gitweb.gentoo.org/proj/pms.git/
|
GitWeb