The location of libhinawa and hinawa-utils for FireWire sound devices ?

The location of libhinawa and hinawa-utils for FireWire sound devices ?

[Takashi Sakamoto]

Hi all,

In this thread, I'd like to discuss about the location of 'libhinawa' and
'hinawa-utils'. Currently, I push them to github.com for my convenience,
while I also think it better to put them in git.alsa-project.org. Then, I
concern about some issues about packaging. Before discussing about the
issues, I'd like you to read my explaination about the aim of these
softwares. (Sorry to take a bit long story...)


This month I concentrated on userspace utilities for some devices
supported by ALSA firewire stack[0]. Today, I released libhinawa 0.7.0.
https://github.com/takaswie/libhinawa

As applications of libhinawa, I wrote some CUI tools as python3
modules/scripts and push them to 'hinawa-utils' repository.
https://github.com/takaswie/hinawa-utils

Currently, below scripts are available in the repository:
 * hinawa-bebob-parser
    * Plug structure parser for BeBoB firmware
 * hinawa-dg00x-cui
    * CUI tool for Digidesign Digi00x family
 * hinawa-dice-common-cui
    * CUI tool for Dice common functionalities
 * hinawa-fireworks-cui
    * CUI tool for Echo Audio Fireworks module
 * hinawa-griffin-firewave-cui
    * CUI tool for Griffin Firewave
 * hinawa-lacie-speakers-cui
    * CUI tool for Lacie FireWire speakers
 * hinawa-maudio-bebob-normal-cui
    * CUI tool for M-Audio FireWire series
 * hinawa-maudio-bebob-special-cui
    * CUI tool for M-Audio FireWire series with largely customized firmware
 * hinawa-oxfw-generic-cui
    * CUI tool for OXFW generic functionalities
 * hinawa-tascam-fireone-cui
    * CUI tool for Tascam FireOne
 * hinawa-tscm-fw-cui
    * CUI tool for Tascam FireWire series
 * hinawa-yamaha-go-cui
    * CUI tool for Yamaha GO series


The 'libhinawa' is I/O library of IEEE 1394 asynchronous transactions
to/from units on IEEE 1394 bus. The aim of this library is to assist
userspace applications to control the physical units. Additionally, this
library supports some ioctl commands which ALSA firewire stack has[1].

The library is written according to GLib/GObject[2] fashion, and supports
GObject Introspection[3] to allow each language implementation to handle
the library. For example, in python3, the library is available via
PyGObject[4]. Totally, the library supports developers to write userspace
applications with their preferable languages.


Well, let me to share my issues. At a beginning of this development, I
planned to merge them to 'alsa-tools.git'[5], and I've posted my first
RFCs as a part of alsa-tools.git. In this repository, there're some
stand-alone applications. But 'libhinawa' includes a shared library and
'hinawa-utils' includes python3 modules, python3 scripts. They're not a
single application.

When we put them to the repository, I can imagine some issues related to
packaging in Linux distribution side, especially, package dependency. The
libhinawa adds new build-dependency to:
 * automake
 * autoconf
 * libtool
 * libglib
 * gtk-doc-tools
 * gobject-introspection
 * libgirepository
Additionally, it adds new runtime-dependency to (not so cleared):
 * python3
 * python-gobject

They will be newly applied to 'alsa-tools' package. It seems to bring
package maintainers to harder work to satisfy the dependency to build
'alsa-tools' package. To me, it's worse cost-effectiveness.

So, currently, I think it better to maintain these two softwares in
github.com, or adds new repository to git.alsa-project.org. I'd like to
get your comments about this issue.

Regards

[0] under 'sound/firewire' of Linux kernel source.
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/sound/firewire
[1] 'include/uapi/sound/firewire.h' of Linux kernel
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/include/uapi/sound/firewire.h
[2] https://developer.gnome.org/gobject/stable/
[3] https://wiki.gnome.org/Projects/GObjectIntrospection
[4] https://wiki.gnome.org/Projects/PyGObject
[5] http://git.alsa-project.org/?p=alsa-tools.git;a=summary
[6] [RFC][PATCH 00/13] alsa-tools: libhinawa for control applications of
FireWire devices
http://mailman.alsa-project.org/pipermail/alsa-devel/2015-January/086969.html


Takashi Sakamoto

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140

Meaning of the name 'hinawa' and the intension

[Takashi Sakamoto]

Hi,

After published libhinwa, I sometimes got a question about the name
of 'hinawa'. Here, I describe it to the persions who are curious.

At first, I split:
FireWire = Fire + Wire

(Japanese/Chinese translation in the meaning)
-> U+706B[0] + U+7E04[1] (in ISO/IEC 10646)

(Japanese translation in the pronounciation)
-> Hi + Nawa

Actually, the meaning of 'Nawa' is near rope. In Japanese history, Hinawa
was used to fire musket guns introduced in Sengoku period, so the musket
gun is called as Hinawa-ju (Ju means general guns). I think there'is a
word in European culture corresponding to the hi-nawa, but I don't know it.

I select this name because in general the name of library (soname) must
be unique in a system. In my case, I judged it better to pick up words
from non-European language group.

[0] U+706B
http://www.unicode.org/cgi-bin/GetUnihanData.pl?codepoint=706b
[1] U+7E04
http://www.unicode.org/cgi-bin/GetUnihanData.pl?codepoint=7e04


Regards

Takashi Sakamoto

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140

About planning of libhinawa ITP to debian project

[Takashi Sakamoto]

Hi,

In this message, I explain about a plan of libhinawa ITP[0] to debian
project. Fortunately, I got a help of a debian package maintainer,
Kentaro Hayashi. He maintains groonga package[1] and experienced
related works[2].

Currently, we plan to work for it in next month, February 2016. I have
no idea about when FTP master acked to our ITP and when the package is
released from debian project.

I with the package will be available as early as possible, and this work
will be a part of his great work as a debian package maintainer.

FYI,

[0] ITP = Intent To Packaging
[1] Debian -- Details of package groonga in sid:
https://packages.debian.org/sid/groonga
[2] Debian Bug report logs - #732055
ITP: groonga -- Fulltext search engine
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732055


Takashi Sakamoto

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140

Re: About planning of libhinawa ITP to debian project

[Takashi Sakamoto]

On Jan 31 2016 20:45, Takashi Sakamoto wrote:
> Hi,
> 
> In this message, I explain about a plan of libhinawa ITP[0] to debian
> project. Fortunately, I got a help of a debian package maintainer,
> Kentaro Hayashi. He maintains groonga package[1] and experienced
> related works[2].
> 
> Currently, we plan to work for it in next month, February 2016. I have
> no idea about when FTP master acked to our ITP and when the package is
> released from debian project.
> 
> I with the package will be available as early as possible, and this work
> will be a part of his great work as a debian package maintainer.
> 
> FYI,
> 
> [0] ITP = Intent To Packaging
> [1] Debian -- Details of package groonga in sid:
> https://packages.debian.org/sid/groonga
> [2] Debian Bug report logs - #732055
> ITP: groonga -- Fulltext search engine
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732055

Mmm. My first post seems not to be blasted by the mail server of
alsa-project.org. Please refer to archive of linux1394devel.

The location of libhinawa and hinawa-utils for FireWire sound devices ?
http://sourceforge.net/p/linux1394/mailman/message/34809347/


Regards

Takashi Sakamoto

Re: About planning of libhinawa ITP to debian project

[Takashi Sakamoto]

Hi all,

On Jan 31 2016 20:45, Takashi Sakamoto wrote:
> In this message, I explain about a plan of libhinawa ITP[0] to debian
> project. Fortunately, I got a help of a debian package maintainer,
> Kentaro Hayashi. He maintains groonga package[1] and experienced
> related works[2].
> 
> Currently, we plan to work for it in next month, February 2016. I have
> no idea about when FTP master acked to our ITP and when the package is
> released from debian project.

Today, we register this to Debian Bug report #813474.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813474

And start RFS (Request For Sponsorship).
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813489

Thanks for Kentaro.

> I with the package will be available as early as possible, and this work
> will be a part of his great work as a debian package maintainer.
> 
> FYI,
> 
> [0] ITP = Intent To Packaging
> [1] Debian -- Details of package groonga in sid:
> https://packages.debian.org/sid/groonga
> [2] Debian Bug report logs - #732055
> ITP: groonga -- Fulltext search engine
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732055

Takashi Sakamoto

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140

Re: About planning of libhinawa ITP to debian project

[Takashi Sakamoto]

Hi,

On Feb 2 2016 23:04, Takashi Sakamoto wrote:
> On Jan 31 2016 20:45, Takashi Sakamoto wrote:
>> In this message, I explain about a plan of libhinawa ITP[0] to debian
>> project. Fortunately, I got a help of a debian package maintainer,
>> Kentaro Hayashi. He maintains groonga package[1] and experienced
>> related works[2].
>>
>> Currently, we plan to work for it in next month, February 2016. I have
>> no idea about when FTP master acked to our ITP and when the package is
>> released from debian project.
> 
> Today, we register this to Debian Bug report #813474.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813474
> 
> And start RFS (Request For Sponsorship).
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813489
> 
> Thanks for Kentaro.

A few days ago, we got a sponsor for the package and yesterday it's in
new queue. Today, a few hours before, I received a notification that the
package was granted and moved to Debian ftp-master server.

In short, the package is in unstable repository and may be released
within a few days. Thanks all.

Now I'm preparing for 'needs-packaging' request [3] to Ubuntu project.
We have 10 days to FeatureFreeze[4] for Ubuntu 16.04 (Xenyal Xerus)[5].

Regards

>> I with the package will be available as early as possible, and this work
>> will be a part of his great work as a debian package maintainer.
>>
>> FYI,
>>
>> [0] ITP = Intent To Packaging
>> [1] Debian -- Details of package groonga in sid:
>> https://packages.debian.org/sid/groonga
>> [2] Debian Bug report logs - #732055
>> ITP: groonga -- Fulltext search engine
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732055

[3] https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
[4] https://wiki.ubuntu.com/FeatureFreeze
[5] https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule


Takashi Sakamoto

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140

Re: About planning of libhinawa ITP to debian project

[Takashi Sakamoto]

Hi,

On Feb 7 2016 12:10, Takashi Sakamoto wrote:
> Hi,
> 
> On Feb 2 2016 23:04, Takashi Sakamoto wrote:
>> On Jan 31 2016 20:45, Takashi Sakamoto wrote:
>>> In this message, I explain about a plan of libhinawa ITP[0] to debian
>>> project. Fortunately, I got a help of a debian package maintainer,
>>> Kentaro Hayashi. He maintains groonga package[1] and experienced
>>> related works[2].
>>>
>>> Currently, we plan to work for it in next month, February 2016. I have
>>> no idea about when FTP master acked to our ITP and when the package is
>>> released from debian project.
>>
>> Today, we register this to Debian Bug report #813474.
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813474
>>
>> And start RFS (Request For Sponsorship).
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813489
>>
>> Thanks for Kentaro.
> 
> A few days ago, we got a sponsor for the package and yesterday it's in
> new queue. Today, a few hours before, I received a notification that the
> package was granted and moved to Debian ftp-master server.
> 
> In short, the package is in unstable repository and may be released
> within a few days. Thanks all.

Now it's in Debian unstable.
https://packages.debian.org/source/unstable/libhinawa

> Now I'm preparing for 'needs-packaging' request [3] to Ubuntu project.
> We have 10 days to FeatureFreeze[4] for Ubuntu 16.04 (Xenyal Xerus)[5].

In Ubuntu project, AutoSync bot imported it and the package is now
available.
https://launchpad.net/ubuntu/+source/libhinawa

Thanks for all ;)

>>> I with the package will be available as early as possible, and this work
>>> will be a part of his great work as a debian package maintainer.
>>>
>>> FYI,
>>>
>>> [0] ITP = Intent To Packaging
>>> [1] Debian -- Details of package groonga in sid:
>>> https://packages.debian.org/sid/groonga
>>> [2] Debian Bug report logs - #732055
>>> ITP: groonga -- Fulltext search engine
>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732055
> 
> [3] https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
> [4] https://wiki.ubuntu.com/FeatureFreeze
> [5] https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule


Takashi Sakamoto