future development/maintenance of rpkg-util

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

I need to step down as a developer/maintainer of rpkg-util
(https://pagure.io/rpkg-util) as I no longer have the incentive or
knowledge required to maintain the project well enough.

The purpose of this tool was to provide a distro-agnostic rpm package
manager - that translates to:

1) it is able to communicate with any dist-git instance out there
2) it requires zero initial setup, i.e. one just needs to place a
valid spec file into a git repo for rpkg command to be able to work
with that repo (and with that package consequently)
3) the git repo with the spec file doesn't need to have the standard
dist-git layout - context of the spec-file can be whatever as long as
the spec properly references the sources
4) it additionally provides set of preproc (very simple templating
language) macros that enable auto-generation of source tarball(s) and
rpm metadata (Name, Version, Release, VCS, changelog, ...) "on-demand"
from the content of the repository (i.e. source files) and its
metadata (i.e. git history). "On-demand" means that these are only
computed and substituted into the spec file when needed (e.g. srpm or
rpm is built).

There are two other ideas that drove the development except "the
distro-agnostic package manager" thing:

* provide the simplest possible way for upstreams to make rpm packages
out of their application sources
* do that while keeping all the standard workflows of a Fedora
packager working (i.e. upload sources, download sources, build srpm,
send package for a build into a build system)

So rpkg-util fuses these two seemingly different things into a single one.

I also had some other ideas, i.e. how to implement creating
distro-specific variation on this tool that doesn't use inheritance
but instead configuration and pluggable commands but this hasn't been
implemented yet. There is also some potential for extending the macro
library that rpkg-util offers or even the preproc (the bash-based
templating language) syntax to provide a more full-fledged templating
language (preproc is supposed to be non-specific to rpm btw. even
though it is currently part of the rpkg-util git repo).

It has found its use mainly in Copr in SCM built method. I don't know
about uses outside of that scope. The project is in a very good shape
currently with only these reported issues:
https://pagure.io/rpkg-util/issues, which might change with time if it
is unmaintained.

So if anyone from RH or outside would like to step-in and take
maintenance / further development of this project, that would be
welcome. I would probably stick around to some extent and provide any
guidance if needed.

Best regards
clime
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux