Doug Ledford <dledford <at> redhat.com> writes:
> The magic words above were "(or get them packaged)". Our separate SCM
> setup really just means they don't want to futz with it. However, if
> the process for an upstream developer was more like:
>
> Develop in their own SCM, push SCM changes to (Fedora/Debian/SuSE
> repos), kick off build process in (Fedora/Debian/SuSE), done.
They'd still have to update the specfile (or equivalent, e.g. the debian/
directory) for the individual distribution. Uploading the tarball isn't the
hard part of packaging, it can even be scripted (and I also don't see how it
would be any easier to push the SCM changes than to upload the release
tarball), updating the specfiles is.
Kevin Kofler
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
