On 09/08/2011 06:45 PM, Michael Tautschnig wrote:
> [...]
>
>> In this case I would get upstream to remove them from git and generate
>> the compressed versions during the Debian package build process. If
>> upstream doesn't want to remove the compressed versions from git then
>> your get-orig-s
[...]
> In this case I would get upstream to remove them from git and generate
> the compressed versions during the Debian package build process. If
> upstream doesn't want to remove the compressed versions from git then
> your get-orig-source target should remove them when creating a tarball
> for
On Thu, Sep 8, 2011 at 5:25 PM, Jan-Pascal van Best wrote:
> Upstream is only GIT, there are no official releases yet (I've asked,
> since the application is already widely used). There is also nothing
> like build time, since upstream more or less advises to use "git clone"
> to put the applicati
On 09/07/2011 04:47 PM, Paul Wise wrote:
> On Wed, Sep 7, 2011 at 4:42 PM, Jan-Pascal van Best wrote:
>
>
>> Some of the compressed .js and .css files in the upstream source are not
>> accompanied by their uncompressed originals. I've now put those in
>> debian/extra_sources, to be able to gener
On Wed, Sep 7, 2011 at 4:42 PM, Jan-Pascal van Best wrote:
> Some of the compressed .js and .css files in the upstream source are not
> accompanied by their uncompressed originals. I've now put those in
> debian/extra_sources, to be able to generate the proper compressed files
> at package build t
Michael, others,
Sorry for the delay after the NAK from ftp-masters. I've prepared a new
version, but there is something I'm now quite sure about.
Some of the compressed .js and .css files in the upstream source are not
accompanied by their uncompressed originals. I've now put those in
debian/ext
6 matches
Mail list logo
