| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
| |
PR: 58572
Submitted by: Jean-Yves Lefort <jylefort@brutele.be>
Approved by: krion (implicit)
|
|
|
|
|
|
|
| |
- Maintainer timeout > 3 weeks
PR: 57286
Submitted by: Ports Fury
|
|
|
|
|
|
|
| |
- Maintainer timeout > 3 weeks
PR: 57357
Submitted by: Ports Fury
|
|
|
|
|
| |
PR: 58381
Submitted by: Ports Fury
|
|
|
|
|
|
|
| |
- Pet portlint
PR: 58543 58064
Submitted by: Fritz Heinrichmeyer, Larry Rosenman
|
|
|
|
|
| |
PR: 58382
Submitted by: Ports Fury
|
|
|
|
| |
in the last commit.
|
|
|
|
|
| |
PR: 58166
Submitted by: Cheng-Lung Sung <clsung@dragon2.net>
|
|
|
|
| |
Submitted by: kris via bento
|
|
|
|
| |
it to 5.0.2 (which I didn't do due to other errors).
|
|
|
|
| |
it IGNORE on XFree86-4.
|
|
|
|
| |
mesagl in its upcoming upgrade.
|
|
|
|
|
| |
PR: 58129
Submitted by: KATO Tsuguru <tkato@prontomail.com>
|
|
|
|
|
| |
Tested on: i386
Submitted by: bento via kris
|
| |
|
|
|
|
| |
Pointy hat to: kris
|
| |
|
|
|
|
|
| |
Submitted by: maintainer (Christian Gusenbauer <c47g@gmx.at>)
Pointed out by: kris via bento
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
They rerolled the tarball to change the manpage. Looks like they added
a new dia.1 right before the release, and forgot to take the old one
out of the tarball.
Extra special thanks to the dia team for not bumping the version number ;;)
Submitted by: "Florian C. Smeets" <flo@kasimir.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Situation:
- The PTP2 driver doesn't work for G5
- The G3 driver can't be used a G5
- So the canon native driver has been tought the G5's id etc ...
- Bumped port revision, since the G5 PTP2 support was in
test status and the G5 canon native driver support
- fixes G5 PTP2 flaws and
- is kind of new functionality
These patches have been sent to the gphoto devel team and
have been included into CVS today. Since yestarday 2.1.3
has been releases this fix will show up in later versions of
libgphoto.
Note 1: when using gphoto --auto-detect unluckily the buggy PTP2 driver
will be autodetected. You then have to choose manually the correct
driver. Easiest way is to use digikam->Setup and to Choose driver called
"Canon PowerShot G5 (normal mode)".
Note 2: If you want to use digikam as non-root user, you have to tweak
permissions of /dev/ugenX and /dev/ugenX.{1,2,3}
I succeded by using the following commands which I put into /etc/rc.local,
thanks to Poul-Henning Kamp:
/sbin/devfs ruleset 10
/sbin/devfs rule applyset
/sbin/devfs rule add path ugen1* mode 666
/sbin/devfs rule show
A working solution for /etc/devfs.rules I didn't find yet.
Approved by: portmgr@freebsd.org (Joe)
|
|
|
|
|
|
|
| |
where he explicitly objected to it. The port is now again NOT buildable
with Intel's icc-7.1.006.
Approved by: maintainer (ache)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
. run the vendor-supplied test automaticly upon building;
. link the vendor-supplied test dynamicly (using -rpath to
force the usage of the just-built library) -- to add another
implicit test of the shared library's validity;
. reword one of the shell commands as ``sed ... file'' instead
of ``cat file | sed ...'';
. modify one of the files to make it properly compilable by the
icc -- gcc was, apparently, optimizing the junk out anyway.
Approved by: maintainer (ache)
|
|
|
|
|
| |
I had to add a PORTEPOCH bump secondary to a poor choice of prerelease
numbering schemes on my part.
|
|
|
|
|
| |
PR: 58241
Submitted by: Ports Fury
|
|
|
|
|
| |
PR: 58240
Submitted by: Ports Fury
|
|
|
|
|
| |
PR: 58243
Submitted by: Ports Fury
|
|
|
|
|
| |
PR: 58242
Submitted by: Ports Fury
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This is a temporary update, because of issues with sound support.
More fixes will be on the way for quicktime, vorbis, ogg, openal, etc...
PR: ports/58231
Submitted by: David Yeske <dyeske@yahoo.com>
|
|
|
|
|
| |
PR: 58220
Submitted by: Ports Fury
|
|
|
|
| |
Reported by: kris
|
|
|
|
| |
address.
|
|
|
|
|
|
|
|
|
| |
> I'm a bit confused here - where am I using the -fpic flag?
It comes from kmod.mk, I think. Anyway, it turns out this is
a bug in kmod.mk and kernel modules are not yet implemented on
amd64. The previous change should be backed out - sorry for
the misleading suggestion.
|
| |
|
|
|
|
|
|
| |
Noticed on: bento
Submitted by: jon@witchspace.com
|
|
|
|
| |
Noticed by: bento via kris
|
|
|
|
|
|
|
| |
mark as broken on i386 for -current (also fails to configure).
Informed maintainer.
Curiously, it seems to configure correctly on ia64.
|
|
|
|
| |
anything else than Wintel.
|
|
|
|
|
|
| |
the lines with \n\
Pointy hat to: roberto
|
|
|
|
|
|
| |
Make it X11BASE/LOCALBASE-clean.
Transfert maintainership to freebsd-ports@ as I don't have a VAIO anymore.
|
|
|
|
|
|
| |
port's problem on automated build environment.
Spotted by: kris
|