#222 Update version number from ./version.sh with setup.py
Closed 5 years ago Opened 5 years ago by rayson.

We want to build container images directly from source not RPMs. It could be much reasonable to update the version number with setup.py not rpmbuild.sh.


@rayson I have a requirement on the rpms.

We want to deploy the same image internally that we publish upstream and deploy to Fedora's production environment. The fedora-infra team has a requirement that all dependencies must come from the Fedora or EPEL repos, which allows them to be sure that all of the components are open source and have passed legal/license review.

They do not require that the app itself be an rpm - it can come directly from the git repo. Only the dependencies must be rpms and come from the Fedora repos.

Understand. Is there a good way to install dependencies from spec file or
something without duplicating them in Dockerfile?

Ralph Bean pagure@pagure.io=E4=BA=8E2018=E5=B9=B48=E6=9C=8810=E6=97=A5 =
=E5=91=A8=E4=BA=94=E4=B8=8A=E5=8D=884:23=E5=86=99=E9=81=93=EF=BC=9A

ralph added a new comment to an issue you are following:
``
@rayson I have a requirement on the rpms.

We want to deploy the same image internally that we publish upstream and
deploy to Fedora's production environment. The fedora-infra team has a
requirement that all dependencies must come from the Fedora or EPEL repos=
,
which allows them to be sure that all of the components are open source a=
nd
have passed legal/license review.

They do not require that the app itself be an rpm - it can come directly
from the git repo. Only the dependencies must be rpms and come from the
Fedora repos.
``

To reply, visit the link below or just reply to this email
https://pagure.io/waiverdb/issue/222

Yes - try dnf -y builddep somespecfile.spec

Closing this one as wontfix. Thanks @rayson!

Metadata Update from @ralph:
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata