Re: Exploded source tree

2017-06-15 Thread Neal Gompa
On Tue, Jun 6, 2017 at 4:47 AM, Michal Sekletar wrote: > On Tue, Jun 6, 2017 at 7:14 AM, Vít Ondruch wrote: > >> So what would be your workflow here? You would start update of the >> package by "fedpkg upload" to upload the new tarball and let dist-git to >> explode it? And what would be next? >

Re: Exploded source tree

2017-06-07 Thread Ken Dreyer
On Tue, Jun 6, 2017 at 6:25 AM, Miroslav Suchý wrote: > Dne 5.6.2017 v 18:59 Richard W.M. Jones napsal(a): >> It would be nice if this was more automated. > > Tito [1] can do it. Also a shout out to https://github.com/softwarefactory-project/rdopkg . This tool can between a "upstream" repo, a dow

Re: Exploded source tree

2017-06-06 Thread Miroslav Suchý
Dne 5.6.2017 v 18:59 Richard W.M. Jones napsal(a): > It would be nice if this was more automated. Tito [1] can do it. You can create branch (or fork from upstream) change in .tito/tito.props tagger to ReleaseTagger and builder to tito.builder.UpstreamBuilder which will change every commit since

Re: Exploded source tree

2017-06-06 Thread Richard W.M. Jones
On Tue, Jun 06, 2017 at 07:14:09AM +0200, Vít Ondruch wrote: > So what would be your workflow here? You would start update of the > package by "fedpkg upload" to upload the new tarball and let dist-git to > explode it? And what would be next? First off, I don't think that the tarball should be sto

Re: Exploded source tree

2017-06-06 Thread Michal Sekletar
On Tue, Jun 6, 2017 at 7:14 AM, Vít Ondruch wrote: > So what would be your workflow here? You would start update of the > package by "fedpkg upload" to upload the new tarball and let dist-git to > explode it? And what would be next? My ideal workflow would be to use pagure (repo with exploded so

Re: Exploded source tree

2017-06-05 Thread Vít Ondruch
Dne 5.6.2017 v 18:59 Richard W.M. Jones napsal(a): > On Mon, Jun 05, 2017 at 01:33:56PM +0200, Vít Ondruch wrote: >> >> Dne 4.6.2017 v 15:22 Richard W.M. Jones napsal(a): >>> Will the second Pagure instance store exploded trees of the upstream >>> software? Will the dist-git RPM source + patches

Re: Exploded source tree

2017-06-05 Thread Richard W.M. Jones
On Mon, Jun 05, 2017 at 01:33:56PM +0200, Vít Ondruch wrote: > > > Dne 4.6.2017 v 15:22 Richard W.M. Jones napsal(a): > > > > Will the second Pagure instance store exploded trees of the upstream > > software? Will the dist-git RPM source + patches form be generated > > from that? > > > > Rich. >

Exploded source tree

2017-06-05 Thread Vít Ondruch
Dne 4.6.2017 v 15:22 Richard W.M. Jones napsal(a): > > Will the second Pagure instance store exploded trees of the upstream > software? Will the dist-git RPM source + patches form be generated > from that? > > Rich. > Hi Rich, Could you elaborate about your use case? Just today, I discussed t