peridot
/
pv2
mirror of https://github.com/peridotbuild/pv2.git
7
0
Fork 0
Code Issues 1 Packages Projects Releases Wiki Activity
pv2: base python module for peridot and development tooling
75 Commits 2 Branches 1 Tag 170 KiB
Python 100%
Go to file
Louis Abel 38405b883b
importer: cleanup should be happening if there's no meta 		2024-03-10 21:45:08 -07:00
.github Add GitImporter and misc changes 2023-07-06 15:49:05 -07:00
doc Start proper readme, add pyproject.toml 2023-06-28 00:26:00 -07:00
examples add find spec file 2023-07-11 11:18:54 -07:00
pv2 importer: cleanup should be happening if there's no meta 2024-03-10 21:45:08 -07:00
.gitignore Mass Update 2023-06-14 00:39:36 -07:00
LICENSE Mass Update 2023-06-14 00:39:36 -07:00
README.md update readme to specify rpmautospec 2024-02-23 12:22:44 -07:00
pyproject.toml pv2: make python 3.9 the minimum 2024-03-10 21:39:31 -07:00

README.md

pv2

pv2 last commit pv2 issues prs

language

license

pv2 is a backend module framework for building and development. Initially designed as a POC to support peridot's potential transition to python, it provides utilities that can be used for developers in and outside of the projects in the RESF (such as Rocky Linux).

Requirements

  • An RPM Distribution

    • Fedora
    • Enterprise Linux 9+ recommended
    • CentOS Stream 9+ recommended

  • Python 3.9 or higher

  • rpm-build

  • A few python modules

    • file-magic (python3-file-magic)
    • GitPython (python3-GitPython or via pip)
    • lxml (python3-lxml or via pip)
    • rpm (python3-rpm)
    • pycurl (python3-pycurl)

  • rpm macros packages (brought in by rpm-build package)

    • *-rpm-macros
    • *-srpm-macros

  • additional packages either in Fedora Linux or EPEL

    • rpmautospec-rpm-macros

Example Scripts

Example scripts are found in the examples directory, which can utilize parts of the pv2 module.

Contributing

If you see a bug or a potential enhancement, we always encourage Pull Requests to be sent in. When sending in your pull request, make sure it is against the development branch. PR's to main will be closed.

To submit a change, we recommend that you do so on GitHub:

  • Fork the repository as necessary
  • Make a new branch based on the development branch - Ensure that it is up-to-date
  • Make your changes
  • Send in the PR for review to our development branch