Hello, Doug.
You wrote 13 сентября 2011 г., 0:05:27:
On 09/12/2011 12:58, Lev Serebryakov wrote:
How could I determine which ports are directly lined with libgcc from
gcc44? ldd?
Yes, that's really the only answer. I have the following function which
would work:
snip
libchk port could
Hello, Lev.
You wrote 13 сентября 2011 г., 11:01:14:
For example, x264 DEPENDS on gcc, (has USE_GCC=4.4+ in Makefile),
but no x264 files are linked with libgcc_s.so or other libraries from
gcc44. It seems, that we need separate USE_GCC_BUILD and USE_GCC_RUN,
as with PERL or PYTHON.
Or,
On 13 Sep 2011 01:36, Gerald Pfeifer ger...@pfeifer.com wrote:
On Sun, 22 May 2011, Doug Barton wrote:
Will @unexec in pkg-plist do the job?
On Mon, 23 May 2011, Wesley Shields wrote:
Are these what you are looking for:
Juergen Dankoweit wrote on 10.09.2011 18:54:
Hello clsung,
sorry that I don't know your right name, so I used prefix of your email
address.
I want to tell you that the download address of clamsmtp has changed. It
is now
http://thewalter.net/stef/software/clamsmtp/clamsmtp-1.10.tar.gz
and not
For example, x264 DEPENDS on gcc, (has USE_GCC=4.4+ in Makefile),
but no x264 files are linked with libgcc_s.so or other libraries from
gcc44. It seems, that we need separate USE_GCC_BUILD and USE_GCC_RUN,
as with PERL or PYTHON.
Or, maybe automate this, as now port system warns
Hi,
If not, see to backups and/or migration in due time. We can't possibly
support software that is unsupported by the vendor, but that's what
We already do. Been working just fine for many years. No I wont
tell you where, because I don't trust you a few other irresponsible
ports crusaders
Matthias Andree wrote:
An obscure piece of software is undesirable (and shouldn't be ported in
the first place).
Bullshit!
I think that suffices. If the discussion is getting emotional, we
should stop it.
No. You should stop advocating killing ports, or leave, or be revoked.
FreeBSD
Hi,
Reference:
From: Doug Barton do...@freebsd.org
Date: Sat, 10 Sep 2011 01:40:27 -0700
Message-id: 4e6b227b.5050...@freebsd.org
Doug Barton wrote:
The way that the FreeBSD project handles deleted ports is to leave them
in the CVS repository, where they are easily
If the author of another package stated that maintenance ceased, that is
no longer the case. Any why let port users fall into this pit? They
You advocate digging the pit. The hole where the ports was.
Cheers,
Julian
--
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich
No, I won't tell you which window manager, because if I want to use it
again I don't want to discover that calling it to the minds of some of
the ports people caused it to be deleted.
That summarises it. I too avoided mentioning a port for fear of the
immature kids who destroy ports. At least
On Mon, 2011-09-12 at 18:46 -0500, Stephen Montgomery-Smith wrote:
I found Michal Varga's critique snarky and unnecessarily sarcastic...
I agree that it was unnecessarily sarcastic. We all make mistakes from
time to time. Michal could have pointed out the mistake and still been
nice
Lev Serebryakov wrote:
Is here console tool, which shows dependency tree of installed ports
from required port to users? pkg_tree performs opposite task.
Maybe this script is helpful:
http://www.secnetix.de/olli/scripts/pkg_dep_view
By default it displays the dependency graph of your
On Tue, 13 Sep 2011 11:10:51 +0200
Michal Varga varga.mic...@gmail.com wrote:
I'm not writing about this for the first time (in fact this is for the
last time, so hey, at least there's something on a positive note), but
it has gradually become nigh impossible to use FreeBSD as a modern
On 09/13/2011 04:10 AM, Michal Varga wrote:
And if it wasn't Gabor's commit that again brought my OS down to
unusable level, it would be the one next week, or if we are lucky, two
to three weeks from now (but that would be probably this year's record).
Because the current procedures in place
on 13/09/2011 10:01 Lev Serebryakov said the following:
libchk port could help, too. But it seems top be broken. It shows,
that system /usr/lib/libstdc++.so.6 depends on gcc44's libgcc_s.so
and it is completely wrong!
I'll fill pr about it!
Most likely there is something wrong in your
Hello, Andriy.
You wrote 13 сентября 2011 г., 17:10:13:
I'll fill pr about it!
Most likely there is something wrong in your environment.
libmap.conf or some such.
it is empty.
libchk uses what ldd(1) reports and ldd reports what would happen during
actual
run-time linking.
ldd run
On Tue, Sep 13, 2011 at 11:10:51AM +0200, Michal Varga wrote:
So believe me, as soon as my systems are all on [insert any modern and
properly maintained desktop OS/distribution that works, which based on
my tests over the last few weeks quite nicely fills Arch Linux, but then
many else would
Stephen Montgomery-Smith wrote:
particularly nasty thing to do. I get the impression that each
committer has his own special way of doing this. For example, I have
personally found that a simple grep won't work, because grep xxx
/usr/ports/*/Makefile* just creates a line too long for
On Mon, Sep 12, 2011 at 11:32:01PM +0200, Julian H. Stacey wrote:
Please consider resigning.
plonk.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
Am 12.09.2011 22:58, schrieb Julian H. Stacey:
If the author of another package stated that maintenance ceased, that is
no longer the case. Any why let port users fall into this pit? They
You advocate digging the pit. The hole where the ports was.
Nonsense. It's a wanton exaggeration of
(redirect from -current@ to -ports@)
Erwin Lansing er...@freebsd.org writes:
On Tue, Sep 13, 2011 at 09:45:05AM +, Thomas Mueller wrote:
PORTSDIR=/BETA1/usr/ports
PACKAGES=/usr/packages
WRKDIR=workb2
# added by use.perl 2011-09-13 02:49:43
PERL_VERSION=5.14.1
Maybe WRKDIR should
Am 13.09.2011 11:10, schrieb Michal Varga:
On Mon, 2011-09-12 at 18:46 -0500, Stephen Montgomery-Smith wrote:
I found Michal Varga's critique snarky and unnecessarily sarcastic...
I agree that it was unnecessarily sarcastic. We all make mistakes from
time to time. Michal could have
Am 12.09.2011 23:32, schrieb Julian H. Stacey:
Hi,
If not, see to backups and/or migration in due time. We can't possibly
support software that is unsupported by the vendor, but that's what
We already do. Been working just fine for many years. No I wont
tell you where, because I don't
On 13 September 2011 17:25, h h aakuu...@gmail.com wrote:
(redirect from -current@ to -ports@)
Erwin Lansing er...@freebsd.org writes:
On Tue, Sep 13, 2011 at 09:45:05AM +, Thomas Mueller wrote:
PORTSDIR=/BETA1/usr/ports
PACKAGES=/usr/packages
WRKDIR=workb2
# added by use.perl
On 12 September 2011 22:07, Julian H. Stacey j...@berklix.com wrote:
No, I won't tell you which window manager, because if I want to use it
again I don't want to discover that calling it to the minds of some of
the ports people caused it to be deleted.
That summarises it. I too avoided
Hi,
Reference:
From: Chris Rees cr...@freebsd.org
Date: Tue, 13 Sep 2011 18:44:37 +0100
Message-id:
cadlo83-zcvaeyznw5dtehv1tosburzllr2hjxfjrx_qewph...@mail.gmail.com
Chris Rees wrote:
On 12 September 2011 22:18, Julian H. Stacey j...@berklix.com wrote:
Matthias
Hello.
Who did the subject and why?
# portupgrade -f -o /usr/ports/mail/exim exim-mysql-4.71
=== exim-4.76 conflicts with installed package(s):
exim-mysql-4.71
They install files into the same place.
You may want to stop build with Ctrl + C.
=== Vulnerability check
Chris Rees wrote:
On 12 September 2011 22:18, Julian H. Stacey j...@berklix.com wrote:
Matthias Andree wrote:
An obscure piece of software is undesirable (and shouldn't be ported in
the first place).
Bullshit!
I think that suffices. If the discussion is getting emotional, we
Stephen Montgomery-Smith wrote on 13.09.2011 16:03:
In particular, checking which ports depend on a port just updated is a
particularly nasty thing to do. I get the impression that each committer
has his own special way of doing this. For example, I have personally
found that a simple grep
Hi,
Reference:
From: Chris Rees cr...@freebsd.org
Date: Tue, 13 Sep 2011 19:25:01 +0100
Message-id:
CADLo838gUfrGhOYWYBym=5yiatyjy8r9bndxcu8gmbjebre...@mail.gmail.com
Chris Rees wrote:
On 13 September 2011 18:54, Julian H. Stacey j...@berklix.com wrote:
Hi,
On 09/13/11 14:27, Michal Varga wrote:
Sigh, okay.
Some time earlier during the day I was still planning to address few
interesting points (especially) Stephen raised, but by this time I'm
finally getting to it and reading through the rest of the emails, I can
see that this would only be a
Hello,
I moved all my servers (about 40) to the pkgng (new generation)
package/port
system, and I can say that it is amazing... it is not yet finish, and
have some
minor issues, but works very well, and is lightning fast..
It is almost the same as pacman (from Archlinux).. you build a
On 13 Sep 2011 20:57, Julian H. Stacey j...@berklix.com wrote:
Hi,
Reference:
From: Chris Rees cr...@freebsd.org
Date: Tue, 13 Sep 2011 19:25:01 +0100
Message-id: CADLo838gUfrGhOYWYBym=
5yiatyjy8r9bndxcu8gmbjebre...@mail.gmail.com
Chris Rees wrote:
On 13 September
On 09/13/2011 03:53, Sergio de Almeida Lenzi wrote:
Hello,
I moved all my servers (about 40) to the pkgng (new generation)
package/port
system, and I can say that it is amazing... it is not yet finish, and
have some
minor issues, but works very well, and is lightning fast..
It is almost the
On 09/13/2011 09:11 AM, Oliver Fromme wrote:
Stephen Montgomery-Smith wrote:
particularly nasty thing to do. I get the impression that each
committer has his own special way of doing this. For example, I have
personally found that a simple grep won't work, because grep xxx
Sergio wrote:
I moved all my servers (about 40) to the pkgng (new generation)
package/port
system, and I can say that it is amazing... it is not yet finish, and
have some
minor issues, but works very well, and is lightning fast..
It is almost the same as pacman (from Archlinux).. you build
On 09/13/2011 23:16, Michel Talon wrote:
Sergio wrote:
I moved all my servers (about 40) to the pkgng (new generation)
package/port
system, and I can say that it is amazing... it is not yet finish, and
have some
minor issues, but works very well, and is lightning fast..
It is almost the same
Am 13.09.2011 21:27, schrieb Michal Varga:
Though if I had to pick a random case again, it probably wouldn't be too
hard to make some wildly unsubstantiated guesses:
## From: Matthias Andree matthias.and...@gmx.de
## Mailer: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.21)
Wildly
Its time that commit bit was revoked to protect ports/ along with
perhaps 3 other misguided butchers' commit bits, perhaps one of
whom might have been your commit mentor.
Get a life.
___
freebsd-ports@freebsd.org mailing list
Matthias Andree wrote:
claim, please fix, until end 2011, in mail/procmail, in collaboration
with sunpoet@:
Procmail works for me, for a friend, others on list.
It was remains irresponsible to try to force satisfied users to fix other
people's reported problems on threat of ports being
On Tue, Sep 13, 2011 at 11:53:54PM +0200, Matthias Andree wrote:
Its time that commit bit was revoked to protect ports/ along with
perhaps 3 other misguided butchers' commit bits, perhaps one of
whom might have been your commit mentor.
Get a life.
The two of you come off like mirror
* Alexey Dokuchaev (da...@freebsd.org) wrote:
Log:
- Update NVidia drivers to their corresponding latest versions
- Apply a workaround to fix the build on recent -CURRENT after fget(9) KPI
was changed in r224778 (affects the driver since version 195.22)
Just for everyone's
On 9/13/11 4:52 PM, Chris Rees wrote:
I'm rather tired of being called to defend myself,
I see no reason why you should find it necessary. Bravo for the work
you've done.
I've plenty of better things to be doing.
Agreed. Julian, amongst others this past few weeks, have successfully
made
43 matches
Mail list logo
