offer it to wider audience for some testing, before
submitting the port as a final product.
At this point, it's not that important trying to figure out the final
part, as you have still kind of a long way ahead of you getting the
program actually working. So, m
onf isn't going away), while most recent Gnome3-era applications
already migrated, or are in the process of migration to dconf (note that
even the base Gnome3 didn't yet fully moved to dconf as of Gnome 3.2)
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
On Tue, 2011-10-11 at 21:39 +0200, Hans Petter Selasky wrote:
> On Tuesday 11 October 2011 21:31:02 Juergen Lock wrote:
> > On Tue, Oct 11, 2011 at 08:35:49PM +0200, Michal Varga wrote:
> > > On Tue, 2011-10-11 at 20:21 +0200, Juergen Lock wrote:
> > > > No. webcamd
any push to rename webcamd to something more meaningful yet?
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
saying that Fluxbox is heavier than KDE3??
>
>
Especially when Fluxbox is a window manager and KDE is an desktop
environment.
Comparing those two on the same scale is like comparing FreeBSD to an
ssh client.
m.
--
Michal Varga,
Stonehenge (Gmail account)
_
with:
# cd /usr/src/usr.bin/xz
# make clean
# make
# make install
[ # make clean ]
> Is there some sensible way to do this?
Force deinstall xz package, run pkgdb -Fuf, confirm deleting the
unneeded dependency (if asked), and you're done.
m.
--
Michal Varga,
Stonehenge (Gmail account)
orking correctly.
>
> dmesg | grep -i geforce
> nvidia0: on vgapci0
>
> This is a FreeBSD-8.2 amd64 machine and the card is not exactly "start
> of the art" either.
>
I'm using 280.13 since the hour it came out (atm on
8.2-STABLE i386) for 2D and 3D graph
. No offense meant, in any case.
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
on the large scale (yes, my FreeBSD servers with a
limited scope of ports still run perfectly fine over the decade, thank
you), but that's but a minor issue that nobody around seems to be
bothered with, so I guess I will be fine too in that case.
m.
--
Michal Varga,
Stonehenge (Gmail
endency tree first, BEFORE committing
just the one port alone, because... If that was happening, what would
then be all those end-users even doing all those empty days, other than
rolling back ports and catching up/fixing breakages? For myself, I
surely can't eve
On Thu, 2011-09-01 at 04:23 -0500, Mark Linimon wrote:
> On Mon, Aug 29, 2011 at 07:34:56AM +0200, Michal Varga wrote:
> > - While nobody probably cares much about that guy and his missing
> > browser images, what would you tell to the GIMP guy? That he should have
> >
is.
>
> Also did a recompile off all the evolution stuff,
> Then tried portmaster lib* in the hope there was a library not installed ok,
> but that ends with the same error as above.
>
> I am struggling for a day or 4 now with this.
>
> Could someone please help me :D
;. It's an issue that won't go away on
its own.
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
n, I can't see how
would PC-BSD help in this case as it's the exact opposite of what I
described. The fact that PC-BSD just tracks ports and builds
self-contained packages from them doesn't automagically make them better
product, it's still the same ports, but now just horribly packa
rner stone of quality control, ports will
only keep rotting further, the more the applications will keep getting
complex and entangled in hundreds and hundreds of dependencies. The
simple fact that port builds isn't, and wasn't for a long time now, an
indicator that the port
unt as a desktop in my book :)
(Ok, just trolling. But who knows...)
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
t' in the overall scheme it is and when it's safe to update
it and when you have to schedule a week-long alarm to let it cool down a
bit until it's (probably) safe to use it (as some other people got
probably burned and hopefully reported it).
This is really a bad idea. When port
On Sun, 2011-08-28 at 14:43 -0700, Doug Barton wrote:
> On 8/28/2011 1:54 PM, Michal Varga wrote:
> > On Sun, 2011-08-28 at 15:30 -0400, Sahil Tandon wrote:
> >
> > [...]
> >> Criminal? Indifference? This sort of troll-ish hyperbole is decidedly
> >> un
rts every other moment.
And just being discontent doesn't yet an attack make, no matter how much
you see it there. Jerry, while obviously sarcastic, wasn't any vulgar as
far as I noticed, and even specifically pointed out in few places that
he is not blaming (if I was y
so. I'd simply consider him angry, as for myself, I
know how many such emails I personally didn't have nerves to send, and
would really, really love to. But somehow I feel, Jerry's is simply a
start and there is much more of this to see in the coming future...
m.
--
Michal Var
with kernel corresponding to those
sources. What kind of "warning" would you be expecting there and what
purpose would it serve?
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.o
l FreeBSD for me, and probably anyone else I know.
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
ing ports, but this in no way cuts it for
currently deployed portupgrade setups, where portupgrade works 'just
fine' (and can work the same for years to come). Deprecate it, or kill
it, and you will only force many current users to keep a local copy,
because it's still easier
master www/p5-libwww
If you use portupgrade, no special treatment is necessary.
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
the already installed libchamplain-0.8.so.1
library (which in turn you had linked against libgnutls.so.40).
For a quick fix (I didn't investigate further), simply remove the old
installed port, and let the new one build in clean environment:
# cd /usr/ports/graphics/libchamplain/
# make deinstall clean
# make install clean
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
eers,
>
Well you're definitely not the only one :)
(Like, hell, is there any other option?)
Still, when such things happen, I just move up/down a digit (to cvsup3.,
cvsup4., cvsup5., etc) without so much complaining, you know - unless
one definitely runs out of numbers...
m.
--
Michal Var
ile"
and replace DISTVERSION with either 270.26 (has support for your board),
or the currently latest (not yet properly listed on the site) 270.41.03:
DISTVERSION?= 270.41.03
then
# cd /usr/ports/x11/nvidia-driver/
# make makesum
# portupgrade -vfu nvidia-driver
And you're don
case someone might be interested and/or wants to
correct me before I get to it later today :)
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsu
, frameworks, libraries
Just a quick thought to the 'discuss' part: Is this (above) really the
best name possible?
I mean "world wide web-webapps" sounds kind of redundant.
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-por
ng into h264 works without any issues too.
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
show" (what the error message basically told you).
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
UI will actually make it there (as, currently, there's not even a
spec finalized for it). Just saying.
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
major Perl upgrades). There are not many of them directly
depending on Python and it always saves from trouble like these.
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/l
On Sat, 2011-03-12 at 22:46 +0100, Michal Varga wrote:
> On Sat, 2011-03-12 at 13:34 -0800, Doug Barton wrote:
> > On 03/12/2011 12:45, Mark Linimon wrote:
> > > On Fri, Mar 11, 2011 at 09:14:50PM -0800, Doug Barton wrote:
> > >> There are way too many things happenin
lve that problem is to open the doors.
> >
> > Would you please offer examples of decisions that you feel that way about?
>
> Clearly it would be inappropriate for me to comment publicly on things
> that were discussed in private, so no, I'm not g
ch for me is, currently, like close to 1000. This probably
wasn't intended.
Also, -a stands for "*", so one of them is superfluous in any case.
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@freebsd.org mailing li
rtualbox+4+freebsd&kp=-1&kl=wt-wt&ka=n&kt=n&kk=-1&ke=-1&ko=s&kj=w&kh=1&kn=1&kb=n&km=l&ku=1
The point being, it's really not that hard if you just spare a minute
here or there looking things up, they're not exactly trying to hide
be the cleanest approach,
I guess? I've quickly checked configure and the detection looks pretty
ordinary as it is now, but atm I don't have enought time to trace it
over every single step, so who knows... Might be just a case of typo
somewhere in there?
m.
--
Michal Varga,
Stonehen
On Wed, 2011-03-02 at 16:26 +0100, Pietro Cerutti wrote:
> On 2011-Mar-02, 15:57, Michal Varga wrote:
> > Out of curiosity - how is it even possible that this update made it as
> > far as into ports tree, when it - at least as I understand from the PR -
> > clearly doesn
en it - at least as I understand from the PR -
clearly doesn't work on *both* *STABLE* *supported* branches and only
goes well with the very latest CURRENT?
Wouldn't a single test run on either 7.x or 8.x before committing the
port reveal this issue? Just my thoughts.
m.
--
Michal Var
maintain it?
If so, then seriously, good luck with that.
> ... can be advantageous?
No.
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsu
On Thu, 2011-01-13 at 14:14 +0200, Eugen-Andrei Gavriloaie wrote:
> So, if anybody can help me with at east an easy to follow tutorial, it would
> be awesome.
>
Could this be of some help?
http://www.freebsd.org/doc/en/books/porters-handbook/own-port.html
m.
--
Michal Varga,
S
And the
current state really makes our mencoder kind of crippled...
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send
o
for this or that reason (I've been a long time clive user myself and
wouldn't go back). I guess you could give it a try in case you already
didn't.
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@freebsd.org mailing l
TING an integral part of any
upgrade process, not just "some half-forgotten text file that one
*should* keep an eye on - but usually only after all hell broke loose".
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@fre
eing somewhat
significant).
Please, don't include it by default for everyone.
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
o serious issues, or in this case - if
someone actually tries to remove the "apache-2.\*" package, only to find
there is no such thing.
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@freebsd.org mailing list
http://lists.fr
your shell and expanded into a list of matching files
from your current working directory, then sent as a parameter to
pkg_delete.
What you were probably trying to do was either
pkg_delete -f portmaster\*
or
pkg_delete -f "portmaster*"
m.
--
Michal Varga,
; >Any feedback is welcome.
>
> Cool idea! Count me as another subscriber.
+1, Subscribed
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To un
river/Makefile"
run `make makesum` and reinstall your driver.
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to &quo
re and there with some minor performance increases.
Could have been much worse, I guess.
m.
--
Michal Varga,
Stonehenge (Gmail account)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, sen
>>> Well, it's a dedicated blade after all :) And those 8 cores seem
>>> pretty nasty, I'm envious.
>>>
>>
>> Well, afaik I even cannot use more than one CPU when building ports.
>> There were plans/rumors that this would change. Does anyone know more
>> about it?
>>
Sure you can, as Boris (below)
> # pkg_info | wc -l
> 457
> #
>
> And this machine is even my package-building station!
>
> Anyway, portupgrade -af took 45 minutes. *g*
>
Well, it's a dedicated blade after all :) And those 8 cores seem
pretty nasty, I'm envious.
That 800+ installed ports are for a regular desktop system,
C
On Wed, Jan 20, 2010 at 2:58 PM, Helmut Schneider wrote:
> # pkg_info -R perl-threaded-5.8.9_3 | grep -v ^p5
> Information for perl-threaded-5.8.9_3:
>
> Required by:
> amavisd-new-2.6.4_4,1
> apache-2.2.14_5
> bsdpan-SNMP-Extension-PassPersist-0.03
> gamin-0.1.10_3
> gio-fam-backend-2.22.4
> glib
On Wed, Jan 20, 2010 at 1:54 PM, Helmut Schneider wrote:
> [...]
> Currently the only solution seems to remove perl.5.8 which as a result
> deletes all dependencies which requires *all* ports to be reinstalled.
>
No way, only if you decide to deinstall everything recursively. What about:
# pkg_d
Basically, this: http://www.phoronix.com/scan.php?page=news_item&px=Nzg3MA
---snip---
Red Hat's Ben Skeggs though has started deleting non-KMS code that is
trimming this NVIDIA X.Org driver by thousands of lines of code. While
user-space mode-setting will no longer work, kernel mode-setting is
the
On Wed, Dec 30, 2009 at 6:47 PM, Howard Goldstein wrote:
> Michal Varga wrote:
>> After the recent boost upgrade to 1.41, net-p2p/deluge needs to be
>> recompiled to actually start, otherwise one just gets a nice
>> crash/deadlock (I didn't investigate as I already re
After the recent boost upgrade to 1.41, net-p2p/deluge needs to be
recompiled to actually start, otherwise one just gets a nice
crash/deadlock (I didn't investigate as I already remember the exactly
same issue with previous boost upgrade, so went directly for
recompilation).
Anyway, just an idea -
On Tue, Dec 29, 2009 at 9:03 PM, Sean C. Farley wrote:
> I am jumping randomly into the thread.
>
> If we want to use some type of "release" for MPlayer based upon a snapshot
> from svn, how about using the same snapshot as used in Fedora (actually RPM
> Fusion)[1]? It has the advantages of alrea
On Tue, Dec 29, 2009 at 7:05 PM, Frank Staals wrote:
> On 12/29/09 14:31, Lars Engels wrote:
>>
>> Quoting Frank Staals :
>>
>>> I know it is not as nice as simply having a port. But if you realy need
>>> the svn-releases for some feature XYZ it may be a (temporary) solution.
>>
>>
>> Are there an
On Mon, Dec 28, 2009 at 3:47 PM, eculp wrote:
>>> I have a "port" for building the latest exported snapshot from SVN, but
>>> it requires manual editing because the extract dir changes daily.
>>
>>
>> Hi,
>>
>> does your port deinstall cleanly ? - I would love to use an mplayer
>> version newer th
On Tue, Apr 14, 2009 at 5:34 PM, Dmitry Morozovsky wrote:
> On Tue, 14 Apr 2009, Michal Varga wrote:
> Yes, it's Gnome Terminal, see $SUBJ ;-)
>
> I just filled 'ssh -e none host' in execute command field.
>
> Before upgrade to 2.26 everything is worked like
On Tue, Apr 14, 2009 at 12:24 PM, Dmitry Morozovsky wrote:
> On Tue, 14 Apr 2009, Michal Varga wrote:
> Yes, seahorse shows me two keyrings; however, deleting "login" one does not
> fix
> the situation: if in the Terminal I try to open tab which ssh's to outer host,
&g
Additional small patch (attached) for ConsoleKit is needed for
'shutdown' from within Gnome to work with gnome-session 2.26.0.90.
Logout alone works even without applying this patch.
Diff is against consolekit-0.3.0_6 (latest).
# cd /usr/local/etc/dbus-1/system.d/
# fetch http://varga.stonehenge.
On Tue, Apr 14, 2009 at 3:13 AM, Dmitry Morozovsky wrote:
> Dear Joe Marcus,
>
> DM> JMC> What versions of gnome-keyring and seahorse do you have?
> DM>
> DM> ma...@revamp:/usr/ports> pkg_info | egrep 'gnome-keyring|seahorse'
> DM> gnome-keyring-2.26.0 A program that keeps passwords and other secr
As noted in my previous email today (
http://lists.freebsd.org/pipermail/freebsd-gnome/2009-April/022096.html
), gnome-session 2.26.0.90 is out, with working session save/restore,
the one that has been exterminated with introduction of Gnome 2.24 and
created an usability nightmare for many desktop
Hi guys,
I know that FreeBSD Gnome team has spread pretty thin in past few
months, but just in case (or as a reminder) - is someone from the
Gnome staff keeping an eye on this issue?
http://bugzilla.gnome.org/show_bug.cgi?id=552387
Basically, the single biggest Gnome regression (ever?) is back to
On Tue, Jan 27, 2009 at 7:05 PM, Garrett Cooper wrote:
>Have you read / followed through UPDATING yet? Everything based on
> xcb has to be rebuilt (I'm still working on fixing my forked up copy of
> xchat2).
> -Garrett
>
Sure, rebuilt the whole xcb path (and much more to that as I was
wip
On Mon, Jan 26, 2009 at 8:20 PM, icemaca wrote:
>
> back to the drawing board then. still baffled why mplayer too
>
Dunno if this is your case, but you may be confused by the way mplayer
GUI is launched. Normally, "mplayer" runs a GUI-less version of
mplayer, and as you have been using gnome/menu/
On Sat, Jan 10, 2009 at 9:01 PM, Doug Barton wrote:
> Michal Varga wrote:
>> Hello guys,
>> I noticed that Gnome 2.24 was commited today along with gnome-session
>> 2.24, so I need to ask - how did FreeBSD Gnome team decide to deal
>> with the recent session manageme
Hello guys,
I noticed that Gnome 2.24 was commited today along with gnome-session
2.24, so I need to ask - how did FreeBSD Gnome team decide to deal
with the recent session management fuckup? I mean this:
http://np237.livejournal.com/22014.html
http://bugzilla.gnome.org/show_bug.cgi?id=552387
http
On Mon, Dec 29, 2008 at 1:34 PM, Ricardo Jesus
wrote:
> No need for a patch. It's simply a matter of sysctl.
>
> Take a look here:
> http://linux-bsd-sharing.blogspot.com/2008/12/tip-enable-sound-on-enemy-territory.html
>
Interesting, so it actually got fixed at around the same time. My
apologies
On Tue, Dec 23, 2008 at 1:48 AM, Garrett Cooper wrote:
> On 12/22/08, Gonzalo Martínez-Sanjuan Sánchez wrote:
>> Hi there!
>>
>> I have a problem with the enemyterritory port using linux compat layer. The
>> game has no sound. The only problem I get its this messagge:
>>
>> --- sound initiali
new porting guidelines and deal with the maintainers". And
he does sound quite reasonable.
m.
--
Michal Varga <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
Stonehenge
Home page: http://varga.stonehenge.sk
___
freebsd-ports@freebsd.org mailin
't confirm that by myself, but have some old coworkers in
various web development companies and they say their clients complain
every other day that their new fancy Flash9 presentations (thus
requiring Flash9 plugin) crash Linux browsers like stock market in 1929.
Of course, it's still
.rb:785:in `initialize'
from /usr/local/sbin/portinstall:221:in `new'
from /usr/local/sbin/portinstall:221:in `main'
from /usr/local/sbin/portinstall:2175
os details:
FreeBSD 7.0-BETA1 #0: Sun Oct 21 15:44:29 CEST 2007 i386
portupgrade-devel-2.3.1
ruby1
On Wed, 2007-10-24 at 13:26 -0500, [EMAIL PROTECTED] wrote:
>
> P.S. Why not ;) Is there any hope in all this for GoogleEarth?
> Probably a very silly question.
>
Not sure if I understand your question, but I see GoogleEarth running
perfectly here:
Google Earth 4.2.0198.2451 (beta)
Build Dat
one game or even Java.
>From the perspective of a common everyday desktop user, I'd call current
2.6 support "fine enough", and we are talking about 7.0 that's not even
out yet. Anyway, good job, Roman and the rest of the team.
Just my two pieces of a random currency.
m.
--
78 matches
Mail list logo
