On 09/25/2013 09:00 PM, Daniel Pocock wrote:
> Is there any convenient way that upstream can generate a clean tarball
> with qmake? In general, is it sufficient to work with a
> github-generated tarball for the tag on a qmake project?
Not tested - and I havent used qmake for some longish time, b
On Wed, Sep 25, 2013 at 9:06 PM, Sune Vuorela wrote:
> Unless for autotools projects where you might want to store pregenerated
> files in the tarball, I've never seen the reason for make dist.
For several of my (admittedly autotools) upstreams I add git2cl in the
dist-hook and now that I have pa
On Wed, Sep 25, 2013 at 07:06:04PM +, Sune Vuorela wrote:
> For all my qmake and cmake based projects, neither that has a make dist,
> I've asked my VCS for a tarball of the tag and blessed that one as 'the
> release'.
+1
Anecdotally, one of my upstreams has a broken tarball which is a git
ex
On 2013-09-25, Daniel Pocock wrote:
> qmake doesn't appear to provide a "make dist" facility, at least not the
> way the project is currently configured.
Unless for autotools projects where you might want to store pregenerated
files in the tarball, I've never seen the reason for make dist.
For a
upstream is using qmake for PostBooks
qmake doesn't appear to provide a "make dist" facility, at least not the
way the project is currently configured.
Consequently, upstream tarballs tend to be snapshots of the developer
workspace, in one case, even including things like submodules,
.gitmodule
5 matches
Mail list logo