[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#751550: RFS: aclock.app/0.4.0-1 [ITA]



Paul Gevers wrote:
> On 04-08-14 22:12, Yavor Doganov wrote:
> > Paul Gevers wrote:
> >> Are there any sources for the png/wav in Resources ?
> > 
> > There's a Blender file (cuckoo.blend) in the top directory.
> 
> Then I really suggest to create the images (and the wav?) from that
> file during building. I share the opinion of many (most?) DD's that
> the only way to make sure that we can build from sources with tools
> available in Debian is to actually do that.

That's news to me.  Only one package in the archive build-depends on
blender (gfpoken) and that is because the upstream build system
invokes blender.  Only three packages build-depend on gimp (gfpoken,
openntd-opengfx, xbmc) -- for the first two gimp is invoked by the
upstream build system, and xbmc uses it to regenerate a logo with
Debian modifications (which looks reasonable).

Using blender to regenerate the png files has no practical benefit, it
will only make the package not buildable on architectures where
blender is not installable or not yet built.

If there is a consensus among DDs that all arch-indep files should be
regenerated during build I suggest to make it legitimate by
documenting it in the Debian Policy.

A far more serious concern is whether the .gorm files will be loadable
with future gnustep-gui releases or editable with future gorm.app
versions.

> In that case, please verify that the blender file is really the
> source of the images and document that fact in either d/copyright or
> in a comment in d/rules

Why should I document this?  I really don't understand this
requirement and where it comes from.

> I found one more thinks to remark:
> 
> The location of icon in the desktop file point to /usr/lib/

AFAICT this is not a bug.


Reply to: