[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-release-team
Subject:    Re: Where to put a lib?
From:       Michael Bobanovic <bobanovic.michael () yahoo ! de>
Date:       2009-03-19 3:48:06
Message-ID: 763444.25659.qm () web24706 ! mail ! ird ! yahoo ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


--- Allen Winter <winter@kde.org> schrieb am Mi, 18.3.2009:
Von: Allen Winter <winter@kde.org>
Betreff: Re: Where to put a lib?
An: "Jeff Mitchell" <mitchell@kde.org>
CC: "KDE release coordination" <release-team@kde.org>
Datum: Mittwoch, 18. März 2009, 12:07

On Monday 16 March 2009 5:33:38 pm you wrote:
> Jeff Mitchell wrote:
> > Allen Winter wrote:
> >> Redirecting to the release team...
> >
> >> On Monday 16 March 2009 9:51:55 am Jeff Mitchell wrote:
> >>> Hi,
> >>>
> >>> We Amarok people have split out our Taglib plugins into
something
> >>> standalone for a couple reasons...partially because we split
out one of
> >>> our helper programs in a separate package (so they can both
depend on
> >>> it), and partially so that other people can use it.  Right
now it lives
> >>> in trunk/playground/multimedia/taglib-extras, but we want to
get it
> >>> released very soon.
> >>>
> >>> Where is the right place to put this?  Keep it living where
it is?  Or
> >>> put it in trunk/kdesupport?  Or...?
> >>>
> >> Is it Qt-only?
> >> If so, it could certainly go into kdesupport.
> >
> > Well, it's Taglib-only.  Its only hard dependency is Taglib,
which
> > itself is in kdesupport.
> >
> > It does have optional support for KDE integration (where it uses
> > KMimeType to help figure out what type of file it is), but this
defaults
> > to Off.
> >
> > Still kdesupport material?
> 
> If there are no objections to the optional KDE integration in
> Taglib-Extras by tomorrow, I will move it to kdesupport.
> 
Jeff,

Just keep in mind that kdesupport is not a dumping ground.
Typically, you must manage everything yourself there.

For example, you need to handle tagging and packaging yourself,
as that is not done automatically.  Of course, there are those
here who can help you.  

-- 
Allen Winter | Software Engineer | 1-888-872-9339
KDAB, Inc. | "Platform-independent software solutions"
http://kdab.com | 1-866-777-5322 (US) | +46-563-540090 (Sweden)
_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

With amarok will be nice that came with EQ. that will be very nice what you think?

Mike



      
[Attachment #5 (text/html)]

<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: \
inherit;"><br><br>--- Allen Winter <i>&lt;winter@kde.org&gt;</i> schrieb am <b>Mi, \
18.3.2009:<br></b><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; \
padding-left: 5px;"><b>Von: Allen Winter &lt;winter@kde.org&gt;<br>Betreff: Re: Where to put a \
lib?<br>An: "Jeff Mitchell" &lt;mitchell@kde.org&gt;<br>CC: "KDE release coordination" \
&lt;release-team@kde.org&gt;<br>Datum: Mittwoch, 18. März 2009, 12:07<br><br></b><pre><b>On Monday 16 \
March 2009 5:33:38 pm you wrote:<br>&gt; Jeff Mitchell wrote:<br>&gt; &gt; Allen Winter wrote:<br>&gt; \
&gt;&gt; Redirecting to the release team...<br>&gt; &gt;<br>&gt; &gt;&gt; On Monday 16 March 2009 9:51:55 \
am Jeff Mitchell wrote:<br>&gt; &gt;&gt;&gt; Hi,<br>&gt; &gt;&gt;&gt;<br>&gt; &gt;&gt;&gt; We Amarok \
people have split out our Taglib plugins into<br>something<br>&gt; &gt;&gt;&gt; standalone for a couple  \
reasons...partially because we split<br>out one of<br>&gt; &gt;&gt;&gt; our helper programs in a separate \
package (so they can both<br>depend on<br>&gt; &gt;&gt;&gt; it), and partially so that other people can \
use it.  Right<br>now it lives<br>&gt; &gt;&gt;&gt; in trunk/playground/multimedia/taglib-extras, but we \
want to<br>get it<br>&gt; &gt;&gt;&gt; released very soon.<br>&gt; &gt;&gt;&gt;<br>&gt; &gt;&gt;&gt; \
Where is the right place to put this?  Keep it living where<br>it is?  Or<br>&gt; &gt;&gt;&gt; put it in \
trunk/kdesupport?  Or...?<br>&gt; &gt;&gt;&gt;<br>&gt; &gt;&gt; Is it Qt-only?<br>&gt; &gt;&gt; If so, it \
could certainly go into kdesupport.<br>&gt; &gt;<br>&gt; &gt; Well, it's Taglib-only.  Its only hard \
dependency is Taglib,<br>which<br>&gt; &gt; itself is in kdesupport.<br>&gt; &gt;<br>&gt; &gt; It does \
have optional support for KDE integration (where it uses<br>&gt; &gt; KMimeType to help figure out what \
type of file it is), but  this<br>defaults<br>&gt; &gt; to Off.<br>&gt; &gt;<br>&gt; &gt; Still \
kdesupport material?<br>&gt; <br>&gt; If there are no objections to the optional KDE integration \
in<br>&gt; Taglib-Extras by tomorrow, I will move it to kdesupport.<br>&gt; <br>Jeff,<br><br>Just keep in \
mind that kdesupport is not a dumping ground.<br>Typically, you must manage everything yourself \
there..<br><br>For example, you need to handle tagging and packaging yourself,<br>as that is not done \
automatically.  Of course, there are those<br>here who can help you.  <br><br>-- <br>Allen Winter | \
Software Engineer | 1-888-872-9339<br>KDAB, Inc. | "Platform-independent software \
solutions"<br>http://kdab.com | 1-866-777-5322 (US) | +46-563-540090 \
(Sweden)<br>_______________________________________________<br>release-team mailing \
list<br>release-team@kde.org<br>https://mail.kde.org/mailman/listinfo/release-team<br><br>With amarok \
will be nice that came with EQ. that will be very nice what  you \
think?<br><br>Mike<br></b></pre></blockquote></td></tr></table><br>


      



_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic