From: Alexander Lukichev <alexander.lukichev@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] openpgm: new package
Date: Tue, 12 Feb 2013 12:08:07 +0200 [thread overview]
Message-ID: <511A1487.2060507@gmail.com> (raw)
In-Reply-To: <20130211151429.682ea550@skate>
Hi, Thomas, All!
On 02/11/2013 04:14 PM, Thomas Petazzoni wrote:
>>> unclear if we should choose libpgm or openpgm. Does the openpgm
>>> projects delivers something else than libpgm?
>> Not as far as I know.
Well, actually yes. It's mostly libpgm but there are also bindings for Perl and GStreamer.
> Then maybe we want to call the package libpgm ?
It is referenced from ZeroMQ (in everything, including scripts and documentation) as OpenPGM. I don't know about other packages using it, though.
It is also referenced from inside the package itself (the subdir is openpgm/pgm/ etc). It seems that only the archive and installed library files have libpgm in their names: everything else is named openpgm.
So, I'll do what you and the community advise but I'd rather call it "OpenPGM implementation of libpgm".
--
Best regards,
Alexander Lukichev
next prev parent reply other threads:[~2013-02-12 10:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 12:30 [Buildroot] [PATCH 1/1] openpgm: new package Alexander Lukichev
2013-02-11 12:45 ` Thomas Petazzoni
2013-02-11 12:49 ` Yann E. MORIN
2013-02-11 12:54 ` Thomas Petazzoni
2013-02-11 13:18 ` Alexander Lukichev
2013-02-11 14:14 ` Thomas Petazzoni
2013-02-12 10:08 ` Alexander Lukichev [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-12 10:47 [Buildroot] [PATCH 0/1] [Re-submitted] " Alexander Lukichev
2013-02-12 10:47 ` [Buildroot] [PATCH 1/1] " Alexander Lukichev
2013-02-12 10:53 ` Thomas Petazzoni
2013-02-12 10:57 ` Alexander Lukichev
2013-02-12 17:47 ` Arnout Vandecappelle
2013-02-13 7:30 ` Alexander Lukichev
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=511A1487.2060507@gmail.com \
--to=alexander.lukichev@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.