Hi, The new 0.1.1 libwnck release does include configure script. I've also added a proper tarball to emerald[1] which also includes the configure script and does not need autotools to be present at build time.
Cheers, Povilas [1] - https://github.com/p12tic/emerald/releases/tag/v0.9.7-beta1 On 10/07/2014 01:02 AM, MENGUAL Jean-Philippe wrote: > Hi, > > Thanks, I've added the proper license in Debian packahe. But is that > normal the new tree has no configure and autogen.sh is empty? > > > Regards, > > Le 05/10/2014 04:51, Povilas Kanapickas a écrit : >> n Ugh, the copyright information was missing or incorrect in two files >> in the tarball. I've fixed that and released a new one, v0.1.1. The >> files in that tarball have the following copyright information: >> >> Files: * >> Copyright: 2013-14 Povilas Kanapickas <[email protected]> >> License: LGPL-2.1+ >> >> Files: doc/*.pl >> m4/compile-binding.m4 >> m4/generate-binding.m4 >> Copyright: 2009 Openismus GmbH <http://www.openismus.com/> >> License: GPL-2+ >> >> Files: tools/m4/class_wnckobject.m4 >> Copyright: 1998-2002, 2006-2008 The gtkmm Development team >> 2002-2004, 2007 The glibmm Development Team >> 2002-2003 The Free Software Foundation >> License: LGPL-2.1+ >> >> Files: doc/*.xsl >> Copyright: 2009 Daniel Elstner <[email protected]> >> License: GPL-2+ >> >> Files: m4/*.m4 >> Copyright: 1996-2011 Free Software Foundation, Inc. >> License: GPL-2+ with libtool exception >> >> Files: m4/install-sh >> Copyright: 1994 X Consortium >> License: BSD 2 clause-like >> >> Files: m4/depcomp >> m4/missing >> m4/compile >> Copyright: 1999-2013 Free Software Foundation, Inc >> License: GPL-2+ >> >> Files: m4/config.guess >> m4/config-sub >> Copyright: 1992-2013 Free Software Foundation, Inc >> License: GPL-3+ >> >> On 05/10/14 04:58, MENGUAL Jean-Philippe wrote: >>> nHi, >>> >>> I started packaging libwnckmm. Can you sum up for me copyright and >>> license? I only see your name in the source, and LGPL. But in the doc, I >>> also see Daniel's name, with GPL. And no synthesis in the source. Do you >>> have a clear idea of license and copxright of all source? >>> >>> Thanks for your help, >>> >>> Regards, >>> >>> Le 04/10/2014 18:49, Povilas Kanapickas a écrit : >>>> Hi, >>>> >>>> For emerald you can package the git repo at the latest tag. >>>> Fortunately, github provides .tar.gz archive for each tag, so you >>>> simplify your workflow by thinking about it as an upstream release >>>> tarball. The release archives can be downloaded from here: >>>> >>>> https://github.com/p12tic/emerald/releases >>>> >>>> As for wnckmm, the release tarball is different to what's tracked in >>>> git repository (it contains a lot of generated files in order not to >>>> depend on tools that have been used to produce them). The release >>>> tarball can be downloaded from here: >>>> >>>> https://github.com/p12tic/wnckmm/releases >>>> >>>> Please let me know if you find any issues. >>>> >>>> Cheers, >>>> Povilas >>>> >>>> On 04/10/14 05:28, MENGUAL Jean-Philippe wrote: >>>>> Hi, >>>>> >>>>> I'll soon start my packaging work. Is there a release or only should I >>>>> package git repo? What's the up-to-date and "stable" date? How can I >>>>> fetch the archive which is newest but stable? I will likely give the >>>>> date of the repo. >>>>> >>>>> Same questions for wnckmm. >>>>> >>>>> Thanks, >>>>> >>>>> Regards, >>>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> dev mailing list >>>> [email protected] >>>> http://lists.compiz.org/mailman/listinfo/dev >>>> >>> >>> >> >> >> _______________________________________________ >> dev mailing list >> [email protected] >> http://lists.compiz.org/mailman/listinfo/dev >> > > _______________________________________________ dev mailing list [email protected] http://lists.compiz.org/mailman/listinfo/dev
