[kde-freebsd] port naming collission

2013-05-18 Thread Kurt Jaeger
Hi!

In February, multimedia/dragon was added as part of the KDE 4.9.5 tree.

At that time, devel/dragon, a scanner/parser generator was already
in the tree since approx. 2.5 years.

I have no idea how package naming collissions are resolved, but
is there any requirement to have a uniq package name ? Is
there a chance to resolve this collission ?

Thanks!


-- 
p...@opsec.eu+49 171 3101372 7 years to go !
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information


[kde-freebsd] Qt4 on FreeBSD 10.0/CURRENT using Clang as the compiler

2013-05-18 Thread Super Bisquit
Is it able to build at the present moment?
If not, will I need to build from source within a user's home directory?
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information


[kde-freebsd] [SVN Commit] area51/PORTS/graphics/digikam-kde4-l10n

2013-05-18 Thread Max Brazhnikov
SVN commit 9241 by makc:

Reset PORTREVISION

 M  +0 -1  Makefile  


___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information


Re: [kde-freebsd] Qt4 on FreeBSD 10.0/CURRENT using Clang as the compiler

2013-05-18 Thread Raphael Kubo da Costa
Super Bisquit  writes:

> Is it able to build at the present moment?

I think so.

> If not, will I need to build from source within a user's home
> directory?

I didn't understand this question.
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information


Re: [kde-freebsd] port naming collission

2013-05-18 Thread Chuck Burns

On 5/18/2013 11:45 AM, Kurt Jaeger wrote:

Hi!

In February, multimedia/dragon was added as part of the KDE 4.9.5 tree.

At that time, devel/dragon, a scanner/parser generator was already
in the tree since approx. 2.5 years.

I have no idea how package naming collissions are resolved, but
is there any requirement to have a uniq package name ? Is
there a chance to resolve this collission ?

Thanks!


Ok.. one is named multimedia/dragon  the other is devel/dragon -- last 
time I checked, multimedia/ != devel/ -- so where is the collision?


Do you mean for packages only? With the new binary packing system, the 
preferred way to call packages is by their category/port name. IE: "pkg 
install devel/dragon" will install that one, whereas "pkg install 
multimedia/dragon" will install the kde media player named Dragon


--
Chuck Burns 

___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information