From: Gregor Jasny <gjasny@googlemail.com>
To: unlisted-recipients:; (no To-header on input)@canuck.infradead.org
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: v4l-utils migrated to autotools
Date: Wed, 18 Jan 2012 14:02:02 +0100 [thread overview]
Message-ID: <4F16C2CA.2090401@googlemail.com> (raw)
In-Reply-To: <4F16C11F.3040108@redhat.com>
On 1/18/12 1:54 PM, Mauro Carvalho Chehab wrote:
> Em 18-01-2012 10:47, Gregor Jasny escreveu:
>> On 1/18/12 1:19 PM, Mauro Carvalho Chehab wrote:
>>> It would be nice to write at the INSTALL what dependencies are needed for
>>> the autotools to work, or, alternatively, to commit the files generated
>>> by the autoreconf -vfi magic spell there [1].
>>
>> The end user gets a tarball created with "make dist" which contains all the m4 files.
>
> Ah, ok. It probably makes sense then to add some scripting at the server to do
> a daily build, as the tarballs aren't updated very often. They're updated only
> at the sub-releases:
> http://linuxtv.org/downloads/v4l-utils/
Judging from the upside-down reports: not the lack of a buildable
tarball but the lack of updated distribution packages is a problem. For
Ubuntu we have a PPA repository with nightly builds:
https://launchpad.net/~libv4l/+archive/development
Do you have similar infrastructure for Fedora / RedHat, too?
Thanks,
Gregor
next prev parent reply other threads:[~2012-01-18 13:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 21:37 v4l-utils migrated to autotools Gregor Jasny
2012-01-17 8:21 ` Hans de Goede
2012-01-18 12:19 ` Mauro Carvalho Chehab
2012-01-18 12:31 ` Rémi Denis-Courmont
2012-01-18 12:43 ` Mauro Carvalho Chehab
2012-01-18 13:01 ` Rémi Denis-Courmont
2012-01-18 12:44 ` Patrick Boettcher
2012-01-18 12:56 ` Gregor Jasny
2012-01-18 13:02 ` Rémi Denis-Courmont
2012-01-18 12:47 ` Gregor Jasny
2012-01-18 12:54 ` Mauro Carvalho Chehab
2012-01-18 13:02 ` Gregor Jasny [this message]
2012-01-18 14:52 ` Mauro Carvalho Chehab
2012-01-18 16:42 ` Theodore Kilgore
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F16C2CA.2090401@googlemail.com \
--to=gjasny@googlemail.com \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).