| 1 | pkgcore-0.1.1 <http://dev.gentooexperimental.org/pkgcore-trac> |
|---|
| 2 | |
|---|
| 3 | These are the release notes for version 0.1.1. Please read them carefully as they |
|---|
| 4 | will clarify the intention of pkgcore, getting around the source, who to |
|---|
| 5 | contact if a bug is found, and finally, how to install it. |
|---|
| 6 | |
|---|
| 7 | |
|---|
| 8 | WHAT IS PKGCORE? |
|---|
| 9 | |
|---|
| 10 | pkgcore is a framework for package management; via appropriate class plugins, |
|---|
| 11 | design should allow for any underlying repository/config/format to be used; |
|---|
| 12 | slackwares tgzs being exempted due to lack of any real metadata, and |
|---|
| 13 | autopackage format being exempted due to the fact they effectively embed the |
|---|
| 14 | manager in each package (pkgcore *does* require being able to treat the pkg as |
|---|
| 15 | data, instead of autopackages method of handing resolution/all manager ops off |
|---|
| 16 | to the package script). |
|---|
| 17 | |
|---|
| 18 | |
|---|
| 19 | WHO TO CONTACT IF I FIND A BUG? |
|---|
| 20 | |
|---|
| 21 | Please submit a bug/ticket via http://dev.gentooexperimental.org/pkgcore-trac |
|---|
| 22 | barring that, please at least send the details to |
|---|
| 23 | pkgcore-dev@googlegroups.com . Please do not use bugs.gentoo.org as the first |
|---|
| 24 | step; any bugs, pkgcore devs should filter before passing up at this point. |
|---|
| 25 | |
|---|
| 26 | |
|---|
| 27 | DOCUMENTATION? |
|---|
| 28 | |
|---|
| 29 | Please look in dev-notes/ ; additionally, the code for the most part has |
|---|
| 30 | docstrings, thus pydoc is a good reference. |
|---|
| 31 | |
|---|
| 32 | For just getting started, dev-notes/developing.rst is a good intro |
|---|
| 33 | |
|---|
| 34 | |
|---|
| 35 | TOOLS? |
|---|
| 36 | |
|---|
| 37 | pquery: generic utility for querying info about repositories, revdeps, pkg |
|---|
| 38 | search, vdb search, etc. |
|---|
| 39 | |
|---|
| 40 | pmerge: generic utility for doing resolution, fetching, merging/unmerging, |
|---|
| 41 | etc. |
|---|
| 42 | |
|---|
| 43 | pregen: script for doing ebuild metadata regeneration; can be parallelized |
|---|
| 44 | |
|---|
| 45 | TESTS? |
|---|
| 46 | |
|---|
| 47 | A standalone test runner is available in sandbox; to run, just execute |
|---|
| 48 | sandbox/test.py . |
|---|
| 49 | Aside from that, our runner of choice is twisteds trial; ran via- |
|---|
| 50 | |
|---|
| 51 | trial pkgcore |
|---|
| 52 | |
|---|
| 53 | if doing development, trial is significantly friendlier; the standalone |
|---|
| 54 | runner is designed to be used mainly for installations of pkgcore, where |
|---|
| 55 | all tests must pass, else installation is aborted. |
|---|
| 56 | |
|---|
| 57 | |
|---|
| 58 | INSTALLING: |
|---|
| 59 | |
|---|
| 60 | pretty simple- |
|---|
| 61 | |
|---|
| 62 | tar jxf pkgcore-0.XX.tar.bz2 |
|---|
| 63 | cd pkgcore-0.XX |
|---|
| 64 | python setup.py build |
|---|
| 65 | |
|---|
| 66 | if after running tests, |
|---|
| 67 | |
|---|
| 68 | cd pkgcore-0.xx |
|---|
| 69 | python setup.py build_ext -if |
|---|
| 70 | sandbox/test.py |
|---|
| 71 | |
|---|
| 72 | finally, installing- |
|---|
| 73 | |
|---|
| 74 | cd pkgcore-0.xx |
|---|
| 75 | python setup.py install |
|---|
| 76 | /bin/bash pkgcore/bin/utilities/register.bash |
|---|
