Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] tovid: new package
Date: Wed, 18 Mar 2015 17:47:14 +0100	[thread overview]
Message-ID: <20150318174714.2e552220@free-electrons.com> (raw)
In-Reply-To: <5509A386.1030107@ou.edu>

Dear Steve Kenton,

On Wed, 18 Mar 2015 11:10:46 -0500, Steve Kenton wrote:

> > Why is this patch needed? Does the documentation build requires
> > additional dependencies?
> Yes, with an SVN checkout it is required to get txt2tags to build the man page
> "To build the manpage, you will need txt2tags:
>     http://txt2tags.sourceforge.net"

Ok, please indicate this in the patch description then.

> >> +	select BR2_PACKAGE_BUSYBOX_SHOW_OTHERS # procps_ng
> > 
> > Can you comment on why specifically procps_ng is needed?
> pgrep and IIRC pkill
> "todisc:assert_dep pgrep "You need the pgrep program to use todisc"

Ok. Then please indicate this as well in a comment above the "select
BR2_PACKAGE_PROCPS_NG" line.

> > Amongst those dependencies, it would be great to denote which ones are
> > actual build dependencies, and which ones are only runtime dependencies.
> I think python is the only build dependency - the rest are runtime
> assuming we kill the man page

Ok, then please say so in a comment in the Config.in file.

Essentially, anything that isn't obvious generally needs a comment
somewhere :-)

> >> +TOVID_SITE = http://tovid.googlecode.com/svn/trunk/tovid
> > 
> > Google Code is closing. Is there a better location for this project? Or
> > is the project planning to move to some other place in the near future ?
> Did not know that, will investigate.

Well, I think it's fine for now, the source URL can always be changed
later when the project moves elsewhere. There have been some changes
recently (today, yesterday, etc.) so the project seems to be maintained.

BTW, I don't remember if I asked: why would you want to run something
such as tovid on an embedded system? What's the final use case?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-03-18 16:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18 15:15 [Buildroot] [PATCH v3 1/1] tovid: new package Steve Kenton
2015-03-18 15:46 ` Thomas Petazzoni
2015-03-18 16:10   ` Steve Kenton
2015-03-18 16:47     ` Thomas Petazzoni [this message]
2015-03-18 17:21       ` Steve Kenton
2015-03-19  8:17         ` Thomas Petazzoni
2015-03-19 15:29           ` Steve Kenton
2015-03-19 15:33             ` Thomas Petazzoni

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=20150318174714.2e552220@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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