[Bug 571019] Review Request v2: libmtag - An advanced C music tagging library with a simple API

bugzilla at redhat.com bugzilla at redhat.com
Thu Nov 4 11:16:50 UTC 2010


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=571019

Felipe Contreras <felipe.contreras at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Flag|needinfo?(felipe.contreras@ |
                   |gmail.com)                  |

--- Comment #5 from Felipe Contreras <felipe.contreras at gmail.com> 2010-11-04 07:16:49 EDT ---
(In reply to comment #3)
> http://people.freedesktop.org/~felipec/fedora/libmtag.spec
> 
> Gives a 404 error...

Fixed.

> Also may I ask why you are packaging libmtag? As it is a library mostly, I
> assume
> you're packaging it for use in something else? I'm asking because for
> sponsering I always find it good when a submitter submits multiple packages in
> one go, this gives me a better chance to get a feeling for how well you know
> the packaging guidelines.

The library is good in itself. The reason I'm packaging it is so I and other
people don't have to manually compile it every time.

I know the packaging guidelines for C libraries, but I have never tried python
or ruby packaging which is how most people are using this library. That's why I
decided to start with the library first.

To be honest, the process to submit packages was painful and demotivational,
and after one year and addressing every comment, there's no light on the end of
the tunnel.

I guess I'll better give up, write compelling UI applications that use this
library, and leave to other people to push for this library, when presumably
you guys would bend over due to public demand.

FTR. This package follows the guidelines already.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



More information about the package-review mailing list