peridot/pv2
7
0
Fork 0
mirror of https://github.com/peridotbuild/pv2.git synced 2024-11-21 12:41:26 +00:00
Code Issues 1 Packages Projects Releases Wiki Activity
pv2: base python module for peridot and development tooling
18 Commits 2 Branches 1 Tag 184 KiB
Python 100%
3488f7ca28
Go to file
Louis Abel 3488f7ca28
Add GitImporter and misc changes 
* Add GitImporter class to importer utility

  * Given a pagure or gitlab source, it should be able to import an rpm

* Added utilitis to handle GitImporter changes
* Modified README for future github transport
* Added issue templates for future github transport
* Raise micro version
2023-07-06 15:49:05 -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 make destination lookaside configurable 2023-07-03 12:43:36 -07:00
pv2 Add GitImporter and misc changes 2023-07-06 15:49:05 -07:00
.gitignore Mass Update 2023-06-14 00:39:36 -07:00
LICENSE Mass Update 2023-06-14 00:39:36 -07:00
pyproject.toml Add GitImporter and misc changes 2023-07-06 15:49:05 -07:00
README.md Add GitImporter and misc changes 2023-07-06 15:49:05 -07:00

README.md

pv2

pv2 is a backend module framework for building and development. Initially designed as a POC to support peridot's 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 8, 9+ recommended
    • CentOS Stream 8, 9+ recommended

  • Python 3.6 or higher - Python 3.9+ recommended

  • 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

    • *-rpm-macros
    • *-srpm-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