t; In general, the answer will be: use qt4-* ports :-(
>
> As soon as a) I know what the equivalent is and b) it compiles
> and runs.
> I am happy to know arts is an indirect dependency (probably
> thought the sdl_*) and mplayer /et al./ will hopefully continue to
>
> Btw: I do not see that mplayer depends on qt3 stuff:
>
> $ pkg_info -r mplayer-1.1.r20130308 | fgrep qt3
>
> > recommended replacement?
>
> In general, the answer will be: use qt4-* ports :-(
As soon as a) I know what the equivalent is and b) it compi
El día Monday, June 10, 2013 a las 08:00:13AM -0400, Robert Huff escribió:
>
> An attempt to rebuild this brought a message saying the port is
> deprecated due to dependency on qt3.
> Considering I have at least a dozen ports listed as
> dependencies - including gimp, sdl_*, and mplay
An attempt to rebuild this brought a message saying the port is
deprecated due to dependency on qt3.
Considering I have at least a dozen ports listed as
dependencies - including gimp, sdl_*, and mplayer - what is the
recommended replacement?
Respectfully,
On Mon, Jul 11, 2011 at 08:51:02AM +1000, Peter Jeremy wrote:
> It would be useful if there was a mechanism to warn users
> that the port they are about to install (or have installed) is no
> longer recommended.
IMHO using DEPRECATED without EXPIRATION_DATE is just fine for this.
mcl
On 2011-Jul-07 23:13:08 +0400, Max Brazhnikov wrote:
>Until ports are not broken or/and forbidden I see no reason for deprecation
>and removing them.
>However you may consider this step as a recommendation to migrate from
>Qt3/KDE3 ports to anything else.
I would suggest that deprecation (witho
On Jul 7, 2011, at 21:13 , Max Brazhnikov wrote:
> On Thu, 07 Jul 2011 11:09:37 -0700, Doug Barton wrote:
>> On 07/07/2011 10:21, Max Brazhnikov wrote:
>>> Reset maintainership de jure. In fact KDE 3 has not been maintained by
>>> our team
>>>
>>> for a long time, not to mention upstream.
>>>
On Thu, 07 Jul 2011 11:09:37 -0700, Doug Barton wrote:
> On 07/07/2011 10:21, Max Brazhnikov wrote:
> > Reset maintainership de jure. In fact KDE 3 has not been maintained by
> > our team
> >
> > for a long time, not to mention upstream.
> >
> > Discussed a while ago among the KDE/FreeBSD t
On 07/07/2011 10:21, Max Brazhnikov wrote:
> Reset maintainership de jure. In fact KDE 3 has not been maintained by our
> team
> for a long time, not to mention upstream.
>
> Discussed a while ago among the KDE/FreeBSD team.
>
Certainly if the ports are not being maintained by kde@ then
ity to fuel a successful career in the Culina ry
Arts. All it takes is talent, a love for food, and the right
training. T= hat's where Le Cordon Bleu Schools North America come in.
Find out more about Le Cordon Bleu's cu= linary programs now.
Whether it's a career in the Culi
Kris Kennaway wrote:
Nah, 5.x is dead and has begun to decompose, but there was a bit of a
mix-up in getting the pre-announcements widely publicized so we decided
to hold off on the burial process ...
JUST what we need, more rotting corpses around here ...
___
Brandon S. Allbery KF8NH wrote:
On 2008 Jun 24, at 19:03, Philip M. Gollucci wrote:
Kris Kennaway wrote:
Philip M. Gollucci wrote:
o Remove 5.x support
Port maintainer ([EMAIL PROTECTED]) is cc'd.
FYI, we stated in the EOL announcement that we are not doing sweeping
5.x removals right awa
On 2008 Jun 24, at 19:03, Philip M. Gollucci wrote:
Kris Kennaway wrote:
Philip M. Gollucci wrote:
o Remove 5.x support
Port maintainer ([EMAIL PROTECTED]) is cc'd.
FYI, we stated in the EOL announcement that we are not doing
sweeping 5.x removals right away. Please give it more time.
I
Kris Kennaway wrote:
Philip M. Gollucci wrote:
o Remove 5.x support
Port maintainer ([EMAIL PROTECTED]) is cc'd.
FYI, we stated in the EOL announcement that we are not doing sweeping
5.x removals right away. Please give it more time.
I thought I waited 2 weeks, anyway, ACK.
___
Philip M. Gollucci wrote:
o Remove 5.x support
Port maintainer ([EMAIL PROTECTED]) is cc'd.
FYI, we stated in the EOL announcement that we are not doing sweeping
5.x removals right away. Please give it more time.
Kris
___
freebsd-ports@freebsd
Hello, we have an updated version of the arts++ package which fixes the
compilation problems with GCC 4.x. The latest version is at
http://www.caida.org/tools/utilities/arts/download/arts++-1.1.a13.tar.gz
Please let me know if you need any additional information.
--
[EMAIL PROTECTED] (Ryan
Young Hyun wrote:
> We've released a new version of net-mgmt/arts++. Would it be possible
> for the ports file to be updated (there is currently no maintainer set
> for it)?
Ok, all set. In addition to the version upgrade, I tuned up the port a bit,
let me know if you see any pr
We've released a new version of net-mgmt/arts++. Would it be
possible for the ports file to be updated (there is currently no
maintainer set for it)?
The latest version is at http://www.caida.org/tools/utilities/arts/
download/arts++-1.1.a12.tar.gz
Please note that the download URL
2006/8/31, Ruslans Baidaks <[EMAIL PROTECTED]>:
It was created by Arts++ configure 1.1.a11, which was
generated by GNU Autoconf 2.53. Invocation command line was
configure:1609: checking for C compiler default output
configure:1612: gcc295 -O2 -pipe -march=pentium4 conftest.c >&a
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by Arts++ configure 1.1.a11, which was
generated by GNU Autoconf 2.53. Invocation command line was
$ ./configure --enable-shared --prefix=/usr/local
20 matches
Mail list logo
