Open befeleme opened 1 year ago
I'm thinking of creating an automode (-a
, --automode
) that would create a specfile:
-t
by default (the current default)%_pyproject_check_import_allow_no_modules
in %check
that ensures buildability of a Python packages without Python modules
That would be the default for e.g. Copr builds from PyPI.The new default would be that pyp2spec creates a specfile which:
License:
field to the packager%check
invokes the standard %pyproject_check_import
with no additional arguments/options--description
and --summary
- either detected or fall back to defaultsOpen questions:
%pyproject_save_files '*' +auto
- keep it or leave it to only automode and detect the modnames from the package metadata (possible to do, but not immediately - I'll have to start parsing the actual package metadata and stop using PyPI API at some point).For the manual mode, I'd generate something like this for now:
# Add top-level Python module names here as arguments, you can use globs
%pyproject_save_files ...
Same for the License tag. I'd rather get something like this:
# No license information obtained, it's up to the packager
License: ...
Or this:
# WARNING, the determined license tag is not allowed in Fedora!
# "Proprietary" not listed in https://docs.fedoraproject.org/en-US/legal/allowed-licenses/
License: Proprietary AND MIT
than a fatal error.
Till now, most of the work went into enabling a smooth automation. User experience for a human user is much poorer. I'd like to track here the ideas how pyp2spec should behave when a real user interacts with it - ideally define a MVP which can be promoted to the community.