Skip to content
/ portage Public
forked from gentoo/portage

Portage Package Manager - this is just a mirror, send patches to <[email protected]>

License

GPL-2.0, Unknown licenses found

Licenses found

GPL-2.0
LICENSE
Unknown
COPYING
Notifications You must be signed in to change notification settings

chewi/portage

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

CI

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 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 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:

# .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:

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:

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

About

Portage Package Manager - this is just a mirror, send patches to <[email protected]>

Resources

License

GPL-2.0, Unknown licenses found

Licenses found

GPL-2.0
LICENSE
Unknown
COPYING

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Python 92.0%
  • Shell 5.8%
  • C 1.5%
  • Meson 0.7%