README.md: Undeprecate tar_scm #462
Conversation
obscpio breaks ability to build packages with rpmbuild. Until that's fixed obscpio should not be used, and hence tar_scm should not be deprecated. Also drop the note about being able to build the obscpio based packages checked out from OBS. Any package can be built locally with osc build but packages *not* based on obscpio can be additionally built with rpmbuild. Signed-off-by: Michal Suchanek <[email protected]>
|
you can run tar also local eg. via "osc service runall". It is a bit pointless with the move to git for packaging, but we won't support tar_scm server side generated tar balls on the long run. |
|
Which means that the tarballs need to be generated locally with tar_scm, and it should not be marked as deprecated. |
|
I don't really see the point of creating the tarball on the server side when there is already and obscpio file. The obscpio file could be used as the source, and rpmextract taught how to extract it. While it is not the source, and the source is not provided the obscpio packages are broken. |
That's exactly what I am doing, only skipping the redundant obscpio step, and having additional set of sources in the package, yet you are saying it's deprecated.
?! how is that relevant at all? |
|
server-side source generation is completely forbidden by server policy |
obscpio breaks ability to build packages with rpmbuild.
Until that's fixed obscpio should not be used, and hence tar_scm should not be deprecated.