Improving our processes for new contributors.

Orion Poplawski orion at
Thu Jul 16 20:12:37 UTC 2015

On 07/16/2015 12:37 PM, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Jul 16, 2015 at 12:14:17PM -0600, Orion Poplawski wrote:
>> On 07/16/2015 11:53 AM, Zbigniew Jędrzejewski-Szmek wrote:
>>> One thing which I find very annoying when creating new packages is the
>>> need to use bare rpmbuild commands. I find the split between
>>> ~/rpmbuild/{SPECS,SOURCES} anachronistic (*), and much prefer the
>>> fedpkg / distgit approach of having everything in one directory.
>>> I now usually use the single directory approach from the beginning:
>>> - git init new-package && cd new-pagkage
>>> - emacs new-package.spec &
>>> - spectool -g *spec
>>> - md5sum ... | tee sources
>>> - git add new-package.spec sources && git commit -m 'Initial version'
>>> - git remote add ssh://
>>> - fedpkg --dist master {srpm,mockbuild,etc}
>>> Without the fake remote fedpkg fails. I am wondering if there is a way
>>> to achieve this in a simpler way, or if not, if it would be possible to
>>> modify fedpkg to support packages which are not part of Fedora out of the
>>> box. IMHO this would make the process easier and more consistent for
>>> new (or existing) contributors.
>>> Zbyszek
>> If I skip creating sources and the git remote add, everything seems to work
>> fine for me with "--dist f21" instead of "--dist master"
> True, sources don't seem to be necessary. There's a warning but it can be ignored.
> Guidelines (and common sense) suggest using rawhide for builds. So adding the
> remote still seems to be necessary.
> Zbyszek

Well, if you know what "rawhide" is, you can just use that, i.e. f24 at the

Orion Poplawski
Technical Manager                     303-415-9701 x222
NWRA, Boulder/CoRA Office             FAX: 303-415-9702
3380 Mitchell Lane                       orion at
Boulder, CO 80301         

More information about the devel mailing list