Re: MP3 licensing over - can we remove LAME restrictions?

[Alex Kozlov]

On Wed, May 03, 2017 at 07:18:18AM +, Ben Woods wrote:
> "On April 23, 2017, Technicolor's mp3 licensing program for certain mp3
> related patents and software of Technicolor and Fraunhofer IIS has been
> terminated."
> http://www.mp3licensing.com/
> 
> It seems that the FreeBSD port for LAME could now have the restriction
> removed, allowing the packages to be available for users by default.
> 
> Perhaps the LAME option could also be enabled by default in ffmpeg?
> 
> Thoughts?
First of all, IMNAL.

But I fear that it's not that simple. Even if the program was terminated,
it doesn't mean that patents are invalidated. And at least one patent from
Fraunhofer IIS is still unexpired: US6185539. Also there is uncertainty
about Alcatel's USRE39080. 


-- 
Alex
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Reducing the size of the ports tree (brainstorm v2)

[Alex Kozlov]

On Sat, Nov 01, 2014 at 12:07:23AM +0100, Tijl Coosemans wrote:
> On Fri, 31 Oct 2014 19:56:21 +0100 Baptiste Daroussin  
> wrote:
> > tijl@ spotted an interesting point, distinfo and pkg-descr files files
> > convenient are taking a lot of space for "free", we can reduce the size of 
> > the
> > while ports tree by a factor 2 by simply merging them into one of the other
> > files (Makefile and/or pkg-plist) from my testing it really devides
> > significantly the size of the tree.
> > 
> > Problem is how to merge them if we want to.
> > 
> > What we do not want to loose:
> > - Easyness of parsing distinfo
> > - Easyness to get informations about the description
> > 
> > so far I have not been able to figure out a user friendly way
> > 
> > Ideas I got so far only concerns pkg-descr:
> > Adding an entry in the Makefile for the WWW:
> > WWW= bla
> > or an entry in the plist: @www http...
> > 
> > for the description the Makefile is not suitable as multi line entry in
> > Makefiles are painful
> > Maybe a new keyword:
> > @descr < > mydesc
> > in 
> > multiline
> > EOD
> > 
> > which could easily be added to the plist parser in pkg. But I'm do not find 
> > that
> > very friendly in particular for make(1) to extract the data.
> > 
> > Concerning the distinfo I have no idea.
> > 
> > so this mail is a call of ideas :), if nothing nice ideas is found we will 
> > just
> > do nothing here :)
> 
> For distinfo I was thinking about something like this in the Makefile:
> 
> DIST_FILES=   FOO BAR
> 
> FOO_FILE= foo-1.0
> FOO_SITES=http://www.example.com/foo/
> FOO_SIZE= 12345
> FOO_SHA256=   0123456789abcdef.
> 
> BAR_FILE= bar-2.0
> BAR_SITES=http://www.example.com/bar/
> BAR_SIZE= 54321
> BAR_SHA256=   .fedcba9876543210
> 
> If bsd.port.mk then contained this:
> DIST_FILES?=  DIST
> DIST_FILE?=   
> ${PORTNAME}-${DISTVERSIONPREFIX}${DISTVERSION}${DISTVERSIONSUFFIX}
> 
> Then for ports with a single distfile named after PORTNAME (the large
> majority), the above would reduce to:
> 
> DIST_SITES=   http://www.example.com/foo/
> DIST_SIZE=12345
> DIST_SHA256=  0123456789abcdef.
> 
> Also, if BAR_SITES is the same as FOO_SITES you can use somthing like
> BAR_SITES=${FOO_SITES} of course.
Yes, it should work, especially if we don't stick to the binary solution:
there are only ~1000 distinfo with more than one distfile and ~350 with more
than two. So, we can embed distfile information for majority of ports
and keep 350 distinfo files. This will allow us to remove 24k+ files. 

> pkg-descr and pkg-plist will be around for a while I think but maybe pkg
> could support an alternative syntax that is similar to the manifest file
> included in the package.  This file (named Manifest maybe?) would include
> a comment, description, install/deinstall scripts and a list of files and
> directories like this (copied from https://github.com/freebsd/pkg):
I don't like embedded files, they are usually not user-serviceable.
We can add WWW variable to the Makefile though, it will greatly speed up
INDEX building.


-- 
Alex
___
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"

Re: [Portlint] Staging warning

[Alex Kozlov]

On Mon, Jul 07, 2014 at 08:34:06PM +0200, A.J. 'Fonz' van Werven wrote:
> [CC: Portlint maintainer]
> 
> Presently, running Portlint on an unstaged port results in a *warning*
> that says "Consider adding STAGE support". I'd surmise that a fatal error
> along the lines of "STAGE support will be mandatory pretty damn soon"
> would be more appropriate.
I've this and other stage issues fixed in my next patch.
I'll submit it in a few next days, it's already long overdue.


-- 
Alex
___
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"

Re: mutt sidebar patch fails after 1.5.22

[Alex Kozlov]

On Sun, Oct 27, 2013 at 01:59:13AM +0900, Koichiro IWAO wrote:
> After recent update to 1.5.22, sidebar patch fails.
There is already pr for this with the updated patch: ports/183251
I'm waiting for confirmation from submitter before commit it.


-- 
Alex
___
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"

Re: [solved] Re: Do not use/install files from STAGEDIR

[Alex Kozlov]

On Mon, Oct 07, 2013 at 11:02:14PM +0400, Boris Samorodov wrote:
> 07.10.2013 21:26, Boris Samorodov пишет:
> 
> > So the question is how to ignore a file from STAGEDIR (i.e. do not
> > include it to a package)?
> 
> As antoine@ wrote by e-mail, one can use post-install target
> to remove a file from STAGEDIR.
It's ok to have orphan files in STAGEDIR. poudriere's check-orphans
error should be just a warning.


-- 
Alex
___
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"

Re: portlint and GETTEXT warning

[Alex Kozlov]

On Sat, Jun 15, 2013 at 02:48:11PM +0400, Boris Samorodov wrote:
> Just FYI: since we now use USES+=gettext the following warning seems
> to be stale:
> -
> WARN: /usr/ports/sysutils/LPRng/pkg-plist: [18]: installing gettext
> translation files, please define USE_GETTEXT as appropriate
> -

There is already pr for this. Please see ports/179338.


-- 
Alex
___
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"

Re: Tool to verify installed package/port consistancy

[Alex Kozlov]

On Fri, May 10, 2013 at 02:17:32PM -0700, Ronald F. Guilmette wrote:
> b.f. bf1783 at googlemail.com wrote:
> 
> >Yes, of course, this is a basic package management feature:
> >pkg_info(1) with the "-g" flag.
> >(The analogous part of the newer pkgng is described in pkg-check(8)
> >from ports-mgmt/pkg.)
> Thank you.  I did not know about the -g option.
For added convenience you can use periodic/security/460.chkpkgsum
(porttools) or periodic/security/460.pkg-checksum (pkgng).
 
> I suppose that I'll have to try to get to the bottom of this.  The
> script that I wrote to do this is so simple, I can't imagine that it
> has a bug that causes just a small subset of the files checked to
> come up as having bad MD5 checksums.  But anything is possible, I
> suppose.
Please investigate this further.


-- 
Alex
___
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"

Re: Should USE_UNZIP be deprecated?

[Alex Kozlov]

On Fri, Dec 21, 2012 at 10:14:10PM -0500, Mikhail T. wrote:
> tar(1) has been able to extract .zip files for quite a while now. Is it 
> time to deprecated USE_UNZIP knob?
External dependency to archivers/unzip will soon be eliminated (see 
ports/172392).
 
> The ports, that use it without also altering 
> EXTRACT_{BEFORE|AFTER}_ARGS, can, probably, be in the first wave -- 
> simply removing the knob from them should do the trick...
unzip in the base for a long time and starting with OSVERSION 117
libarchive have all necessary features to properly handle archive permission.

> For the rest, portlint can be taught to warn about it...
> 
> Or do we still support OS-releases, where tar was not so advanced? Thanks,


-- 
Alex
___
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"

Re: INDEX build failed for 7.x

[Alex Kozlov]

On Fri, Nov 02, 2012 at 12:53:06PM +, Erwin Lansing wrote:
> INDEX build failed with errors:
> Generating INDEX-7 - please wait.. Done.
> make_index: cfv-1.18.3: no entry for /usr/ports/security/py-fchksum
> 
> Committers on the hook:
>  ak bf crees lwhsu olgeni pawel rm 
> 
> Most recent SVN update was:
> Updating '.':
> Udevel/jenkins/distinfo
> Udevel/jenkins/Makefile
> Usysutils/webmin/distinfo
> Usysutils/webmin/Makefile
> Usysutils/virtualmin/distinfo
> Usysutils/virtualmin/pkg-plist
> Usysutils/virtualmin/Makefile
> Utextproc/py-chardet/pkg-descr
> Utextproc/py-chardet/Makefile
> Ugraphics/tesseract/distinfo
> Dsecurity/py-fchksum
Sorry, my fault.


-- 
Alex
___
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"

Re: FreeBSD Port: vtwm-5.4.7_3

[Alex Kozlov]

On Fri, Oct 26, 2012 at 02:13:06AM +, Abc Xyz wrote:
> Why is "rplay" being packaged with VTWM?
> VTWM is supposed to be a minimal no-frills
> window manager (I have used it for 15 years)
> and I very much dislike the added dependencies
> for things I don't care to use and violate the
> spirit of VTWM.  I wrote the programmer that
> did this hack several years ago when he first
> did it, and he promised he would undo it.
> And now, I see it back again (still using 4.11,
> was thinking of upgrading to 9.1).
> 
> Please keep VTWM *minimal*.  If someone wants
> fancy things like "network sound", I am sure
> one of the more fancy window managers will do.
I understand your concern, after all, first thing I did with this port
was make rplay dependency optional. But I don't think it's a good idea
to turn it off by default. The upstream has this option on in default
configuration and port also has sound option enabled for many years.

If you want to get rid of rplay dependency, just rebuild the port
with sound option off.

As a side note, I plan to update vtwm port to 5.5.0-2012-04-25 snapshot at
the end of this year. It's stable, brings many improvements like png support,
sloppy focus, etc and many bug fixes. I've waited long enough, too long perhaps,
for 5.5.0 release.


-- 
Alex
___
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"

Re: Wesnoth Port

[Alex Kozlov]

On Mon, Jul 09, 2012 at 12:40:07PM -0500, Rusty Nejdl wrote:
> I would be willing to take over maintainership of the Wesnoth port as I 
> see Philip just gave it up.  I am already maintaining a few other ports.
Ok. I will commit ports/169144 and update maintainer soon.


-- 
Alex
___
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"

Re: X11BASE still in use in ports

[Alex Kozlov]

On Sun, Jun 24, 2012 at 03:46:40AM -0700, Doug Barton wrote:
> I noticed a failure in one of my ports today while doing an upgrade, and
> was embarrassed to find that it was due to my port still using X11BASE.
> That led me to do a quick grep of the tree, which seems to indicate that
> there are a non-zero number of uses of it which seem to be erroneous:
> 
> http://people.freebsd.org/~dougb/x11base-ports.txt
> 
> Note, some of these are actually Ok, I haven't made an attempt to filter
> them out yet.
> 
> Is there any interest in cleaning these up? Should we restore the
> definition of X11BASE until all of the ports that are using it are fixed?
> 
> I'm kind of surprised by this problem, since the usual way of removing
> something like this is to make sure all of the consumers have been fixed
> first.
I have done a basic analysis. Ports that need to be fixed ('?' - not sure,
'' - should be deleted):  http://people.freebsd.org/~ak/x11base.log


-- 
Alex
___
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"

Re: Wesnoth 1.10.3

[Alex Kozlov]

On Sun, Jun 03, 2012 at 04:36:53PM +0100, Florent P. wrote:
> Hello,
> 
> Is Battle for Wesnoth (games/wesnoth) planed to be upgraded to 1.10.3 ?
Yes, I plan to upgrade games/wesnoth to 1.10.3 and mark
games/wesnoth-devel broken soon.


-- 
Alex
___
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"

Re: Where are conventions like -devel ports documented?

[Alex Kozlov]

On Sun, Mar 25, 2012 at 11:24:59PM +0300, Gerald Pfeifer wrote:
> Perhaps I am missing the obvious and will be rewarded with
> embarrassement, but where are conventions like the use and
> naming of -devel ports described?
> 
> I would have expected this to be covered in
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html
> but -- it is not.
> 
> (If this is an omission, can someone more closely involved than
> I have been so far donate a paragraph or two?)
> 
> Gerald
> 
> PS: I am thinking to split the existing emulators/wine port into
> two, the regular one (tracking releases of Wine) and a -devel port
> that tracks the bi-weekly snapshots that will lead to the next
> release in a year or two.  Somehow I would prefer something like
> wine-stable / wine instead of wine / wine-devel, but the latter is
> more in line with how we are doing things, right?
In general, $port / $port-devel more common, but in case of wine I think
wine-stable or even wine14 / wine would be better. I suspect that not mouch
people would stick with wine release.


--
Adios
___
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"

Re: Making 8.3 packaged ports 'pretty'... and INSTALL_ICONS macro.

[Alex Kozlov]

On Thu, Feb 16, 2012 at 07:54:23AM -0500, Michael Scheidell wrote:
> In looking at some of the prs, minor ones, (safe ones) which just
> upgrades, I noticed one that is a kde4/q4t program,
> portlint complains (a little)
>
> WARN: deskutils/plasma-applet-cwp/pkg-plist: [36]: installing icons,
> please define INSTALLS_ICONS as appropriate
> WARN: deskutils/plasma-applet-cwp/pkg-plist: [37]: installing icons,
> please define INSTALLS_ICONS as appropriate
>
> putting in INSTALLS_ICONS=yes in Makefile, keeps it quiet, but what are
> the side affects of this? does it affect pkg-plist, does it affect 'non
> gnome' programs?
This option adds a graphics/gtk-update-icon-cache dependency (plus all of
its dependencies) and runs gtk-update-icon-cache to update gtk icon cache.

Please also see ports/162260.


--
Adios
___
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"

Re: Yikes: ports/157174: fix typos and small mistakes in various ports

[Alex Kozlov]

On Wed, Feb 15, 2012 at 07:49:06AM -0500, Michael Scheidell wrote:
> On 2/15/12 7:15 AM, Alex Kozlov wrote:
>> Many of those errors was already fixed, thanks to eadler@
>> I will upload updated list.
> can we get them all, and get them /correct/ before the port freeze?
> (thanks Alex.. wish I had seen the list earlier, )
Isn't ports tree go in a slush instead of full freeze during the release?


--
Adios
___
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"

Re: Yikes: ports/157174: fix typos and small mistakes in various ports

[Alex Kozlov]

On Wed, Feb 15, 2012 at 04:03:35PM +0400, Ruslan Mahmatkhanov wrote:
> Michael Scheidell wrote on 15.02.2012 15:56:
>> just spotted this on the eve of the 8.3 freeze.
>> Yikes!
>> lots of ports affected, many typo's. surprised some of these built.
Many of those errors was already fixed, thanks to eadler@
I will upload updated list.

>> 
> Missing SIZE it's an actually lack of '\n' in SIZE line.
Yes, but it's still an error.


--
Adios
___
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"

Re: archivers/zip in 9.x:

[Alex Kozlov]

On Tue, Jan 10, 2012 at 01:06:04AM +0400, Ruslan Mahmatkhanov wrote:
> Michael Scheidell wrote on 10.01.2012 00:30:
>> I think I saw something in the list that FreeBSD 9.x has zip already
>> built in? so, ports that need 'zip' won't need zip?
>>
>> for maintainers, they should use something like:
>>
>> USE_ZIP= yes
>>
>> to:
>>
>> if ${OSVERSION} <= 90
>> USE_ZIP= yes
>> .endif
>>
>> and/or BUILD_DEPENDS+= zip:${PORTSDIR}/archivers/zip
>>
>> (at what OSVERSION was zip included in the base?)
> unzip, not zip. I believe it should be handled in bsd.port.mk like it
> done for USE_XZ. Something like:
>
> .if defined(USE_ZIP) && ${OSVERSION} < 90
> EXTRACT_DEPENDS+=   ${LOCALBASE}/bin/unzip:${PORTSDIR}/archivers/unzip
> .endif
>
> Correct OSVERSION should be used instead of 90. There is also should
> be some logic for UNZIP_CMD.
A few things need to be done before it will be possible to use the
native unzip in CURRENT:
1) pr153429
2) mfv libarchive's seekable zip reader
3) patch to bsd.port.mk which implements USE_ZIP = yes|native|infozip
4) few tinderbox runs


--
Adios
___
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"

Re: Heads Up: X11BASE removal

[Alex Kozlov]

On Mon, Dec 26, 2011 at 08:07:23AM +, Chris Rees wrote:
> On 26 Dec 2011 06:57, "Alex Kozlov"  wrote:
>> On Sun, Dec 25, 2011 at 09:22:02PM -0500, Eitan Adler wrote:
> >> The X11BASE variable has been deprecated for a long time. Support for
> >> having a X11BASE different than LOCALBASE was terminated on
> >> 2009/12/18. After the 9.0 release I will commit a patch that removes
> >> all current references of the variable from bsd.port.mk and
> >> bsd.xorg.mk.  In the meantime I will be adding some helper code to a
> >> few ports that still depend on it. New ports should not reference
> >> X11BASE at all.
>> Do You consider removal of X11 dir from /etc/mtree/BSD.root.dist in
> CURRENT?
>> Old insallations already have this dir and new doesn't have xorg.conf at
>> all or have it in $PREFIX/etc/X11/
> X11BASE is the variable that used to reference /usr/X11R6 which is where
> the older XFree86 was installed.  Since we moved to Xorg, it's been a
> symlink to /usr/local if present.
>
> /etc/X11 is not related to this change.
I know. I saw this topic and remember about remnants of X11 in the base.
Don't want to hijack this thread, so better move to another list.
Where to? current, arch?


--
Adios
___
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"

Re: Heads Up: X11BASE removal

[Alex Kozlov]

On Sun, Dec 25, 2011 at 09:22:02PM -0500, Eitan Adler wrote:
> The X11BASE variable has been deprecated for a long time. Support for
> having a X11BASE different than LOCALBASE was terminated on
> 2009/12/18. After the 9.0 release I will commit a patch that removes
> all current references of the variable from bsd.port.mk and
> bsd.xorg.mk.  In the meantime I will be adding some helper code to a
> few ports that still depend on it. New ports should not reference
> X11BASE at all.
Do You consider removal of X11 dir from /etc/mtree/BSD.root.dist in CURRENT?
Old insallations already have this dir and new doesn't have xorg.conf at
all or have it in $PREFIX/etc/X11/


--
Adios
___
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"

Re: INDEX build for 10-CURRENT

[Alex Kozlov]

On Mon, Sep 26, 2011 at 12:01:47PM +0200, Erwin Lansing wrote:
>> When we can expect INDEX-10.bz2 on http://www.FreeBSD.org/ports/ ? :-)
> Later today.  Running a test run as we speak :-)
What about INDEX-9, DESCRIBE.9 / INDEX-10, DESCRIBE.10 for portsnap?


--
Adios
___
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"

Re: archivers/unzip vs tar -xf

[Alex Kozlov]

On Mon, Jun 06, 2011 at 11:50:36AM -0700, Xin LI wrote:
> On Mon, Jun 6, 2011 at 10:20 AM, Eir Nym  wrote:
>> Since FreeBSD 5.4.0-Release libarchive(3) support to unpack zip files.
>> Why not to use it to unpack distributives to workdir?
>>
>> I've downloaded all distros and tried to unpack them all with tar(1)
>> with no problems. I use FreeBSD 9.0-CURRENT r222717.
> I think the reason is that at the beginning tar(1) does not work for a
> little fraction of distfiles, but yes, I think it's reasonable to take
> a step forward and add a new option to force using the info-zip
> implementation.
Firstly, pr153429 need to be committed, after this exp-run with native
unzip must be done. While only 4-5 distributives can't be extracted by native
unzip, problem with incorrect permissions after extraction exists in
significant numbers of cases.


--
Adios
___
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"

Re: graphics/simpleviewer doesn't build on head(?)

[Alex Kozlov]

On Fri, Apr 08, 2011 at 07:07:02AM +, Alexey Dokuchaev wrote:
> On Fri, Apr 08, 2011 at 01:50:27AM -0500, Zhihao Yuan wrote:
>> Whatever... I don't like this image viewer.
> 
> While this viewer is far from perfect, I find that it at least works
> (contrary to gliv which dumps core on me both now and many years ago
> when I first discovered it) and performs scaling correctly (unlike pho,
> which is currently my viewer of choice).
> 
> I'd happily switch to anything at least as good as default viewer in
> windoze xp, but have not seen anything decent so far.  Maybe you can
> recommend something which is not part of Gnome or KDE?
xv? ;)


--
Adios
___
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"

Re: ports/graphics/netpbm out of date

[Alex Kozlov]

On Wed, Mar 30, 2011 at 08:55:19PM +0200, Dirk Meyer wrote:
> Alex Kozlov schrieb:,
> 
>> So why netpbm is 10.26.64 and graphics/netpbm-devel(??) is 10.35.80?
> 
> Because this is the last released tarball.
> Later Version are only in Subversion.

> 2. - Subversion gives no reproduceable files:
> Fetching a tarball from Viewvc service results in different files each time.
> 
> 3. - No checksum for the release.
> 
> The port can not validate the checksum.
You can fetch wanted version from svn, make a tarball,
place it on ${MASTER_SITE_LOCAL}, and point MASTER_SITES to it.
This will allow update netpbm to 10.47.27 and netpbm-devel to 10.53.05


--
Adios
___
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"

Re: ports/graphics/netpbm out of date

[Alex Kozlov]

On Wed, Mar 30, 2011 at 04:45:03PM +1100, Peter Jeremy wrote:
> On 2011-Mar-29 13:51:21 +0200, Oliver Fromme  wrote:
>>Both graphics/netpbm and graphics/netpbm-devel are *WAY*
>>out of date (5 to 6 years).
> 
> I don't understand you.  In my experience, the netpbm ports have
> always been updated fairly regularly.  The ports currently have:
> STABLE_PORTVERSION= 10.26.64
> DEVEL_PORTVERSION=  10.35.80
> 
> 10.26.64 is the last of the 10.26 series and was released
> almost exactly 18 months ago.
> 
> 10.35.80 is the current "stable" version and was released 
> about 5 weeks ago.  The port was updated the day following
> the release.
>From netpbm website(http://netpbm.sourceforge.net/release.html):

Advanced: This series stabilizes for about a quarter year, then is rebased
to the then-current Development release. That's typically bug fixes, but
some enhancements fit the category and some bug fixes do not. 
"Stabilizes" means that new releases contain only low risk high reward
changes from the previous release.

Stable: This is like Advanced, except that it gets rebased to the
then-current Advanced release instead of Development, which means it the
current release always has at least 3 months of stabilization. 
When it is time to rebase the Advanced series, if the current Stable
release has gone a whole quarter year with no reported bug, we move all
the current releases down one series: Stable becomes Super Stable, then
Advanced becomes Stable, then Development becomes Advanced.
At the 
moment(http://netpbm.svn.sourceforge.net/viewvc/netpbm/stable/version.mk?view=log):
 10.47.27

Super Stable:
The current release in this series has no known bugs and virtually no
undiscovered bugs in it. It may be years behind in new function.
At the moment(http://sourceforge.net/projects/netpbm/files): 10.35.80


So why netpbm is 10.26.64 and graphics/netpbm-devel(??) is 10.35.80?

>>Is anybody working on updating the netpbm ports?  Is there
>>any problem with it that I'm not aware of?
> A quick check would have identified the maintainer (now Cc'd).
Sigh.


--
Adios
___
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"

Re: SDL, perl and frozen-bubble: core dumped

[Alex Kozlov]

On Sat, Mar 12, 2011 at 11:12:38AM +0300, Boris Samorodov wrote:
> On Sat, 12 Mar 2011 06:43:51 +0200 Alex Kozlov wrote:
>> On Fri, Mar 11, 2011 at 05:02:14PM +0300, Boris Samorodov wrote:
> >> On Fri, 11 Mar 2011 14:33:00 +0200 Alex Kozlov wrote:
> >>> On Fri, Mar 11, 2011 at 02:34:44PM +0300, Boris Samorodov wrote:
> > >>> On Fri, 11 Mar 2011 12:44:12 +0200 Alex Kozlov wrote:
> > >>>> On Fri, Mar 11, 2011 at 01:06:35PM +0300, Boris Samorodov wrote:
> > > >>>> I've got a core dump at clang compiled current. The game is starting,
> > > >>>> playing the music and coredumps right after displaying the menu:
> > >>>> Please show perl -V | grep -- -Dusethreads=y && echo threaded
> > >>> 
> > >>> Here it is:
> > >>> -
> > >>> % perl -V | grep -- -Dusethreads=y && echo threaded
> > >>> config_args='-sde -Dprefix=/usr/local 
> > >>> -Darchlib=/usr/local/lib/perl5/5.10.1/mach
> > >>> -Dprivlib=/usr/local/lib/perl5/5.10.1 
> > >>> -Dman3dir=/usr/local/lib/perl5/5.10.1/perl/man/man3
> > >>> -Dman1dir=/usr/local/man/man1 
> > >>> -Dsitearch=/usr/local/lib/perl5/site_perl/5.10.1/mach
> > >>> -Dsitelib=/usr/local/lib/perl5/site_perl/5.10.1 
> > >>> -Dscriptdir=/usr/local/bin
> > >>> -Dsiteman3dir=/usr/local/lib/perl5/5.10.1/man/man3 
> > >>> -Dsiteman1dir=/usr/local/man/man1
> > >>> -Ui_malloc -Ui_iconv -Uinstallusrbinperl -Dcc=cc -Duseshrplib 
> > >>> -Dinc_version_list=none
> > >>> -Dccflags=-DAPPLLIB_EXP="/usr/local/lib/perl5/5.10.1/BSDPAN" 
> > >>> -Doptimize=-g -DDEBUGGING
> > >>> -Ud_dosuid -Ui_gdbm -Dusethreads=y -Dusemymalloc=n -Duse64bitint'
> > >>> threaded
> >>> Interesting. I have a perl 5.8.9, similiar config_args except for 
> >>> -Dusemymalloc=y and
> >>> without -Doptimize=-g, -DDEBUGGING. Fresh current, i386, compiled with 
> >>> gcc.
> >>> frozen-bubble run ok.
> >>> Do You run latest perl-sdl 2.2.6?
> >> Yes:
> >>> Did You rebuild it after upgrade to 5.10.1 perl version? 
> >> Yes.
> >>> Is game also crash without LD_PRELOAD=/usr/lib/libpthread.so?
> >> Yes, just the same.
>> I have upgraded perl to 5.10.1, but unfortunatelly could not run the game:
>> Graphicsrotate_bicubic: orig surface must be 32bpp (bytes per pixel = 1)
>> Perhaps because some time ago I have switched to ati and xf86-video-ati
>> from nvidia blob. Sigh.
>> Anyway, can You please downgrade perl-sdl to previous port version
>> (but keep p5-YAML dependency) and see if this help?
> 
> OK, I downgraded perl and p5 ports to 5.8.9 and p5-SDL to 2.2.0.
> The result is:
> -
> % frozen-bubble
> Bareword "SDL_SRCALPHA" not allowed while "strict subs" in use at 
> /usr/local/lib/perl5/site_perl/5.8.9/mach/FBLE.pm line 130.
> Compilation failed in require at /usr/local/bin/frozen-bubble line 69.
> BEGIN failed--compilation aborted at /usr/local/bin/frozen-bubble line 69.
> %
You can change SDL_SRCALPHA to 65536, but something broken here. 
perl-sdl 2.2.0 have SDL_SRCALPHA:
$grep SDL_SRCALPHA -r *
lib/SDL/Constants.pm:   SDL_SRCALPHA
lib/SDL/Constants.pm:sub SDL_SRCALPHA {65536}
lib/SDL/Surface.pm: SDL_RLEACCELSDL_SRCALPHA
scripts/sdl_words.txt:SDL_SRCALPHA
scripts/SDL/Constants.pm:sub main::SDL_SRCALPHA { 65536 }

Btw, I found a similar problem report, without solution:
http://www.gentooforum.de/artikel/18751/frozen-bubble-l-sst-sich-leider-nicht-starten.html?s=c1bbcc174d5946153f4febd405413dbc7c7a7c1d


--
Adios
___
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"

Re: SDL, perl and frozen-bubble: core dumped

[Alex Kozlov]

On Fri, Mar 11, 2011 at 05:02:14PM +0300, Boris Samorodov wrote:
> On Fri, 11 Mar 2011 14:33:00 +0200 Alex Kozlov wrote:
>> On Fri, Mar 11, 2011 at 02:34:44PM +0300, Boris Samorodov wrote:
> >> On Fri, 11 Mar 2011 12:44:12 +0200 Alex Kozlov wrote:
> >>> On Fri, Mar 11, 2011 at 01:06:35PM +0300, Boris Samorodov wrote:
> > >>> I've got a core dump at clang compiled current. The game is starting,
> > >>> playing the music and coredumps right after displaying the menu:
> >>> Please show perl -V | grep -- -Dusethreads=y && echo threaded
> >> 
> >> Here it is:
> >> -
> >> % perl -V | grep -- -Dusethreads=y && echo threaded
> >> config_args='-sde -Dprefix=/usr/local 
> >> -Darchlib=/usr/local/lib/perl5/5.10.1/mach
> >> -Dprivlib=/usr/local/lib/perl5/5.10.1 
> >> -Dman3dir=/usr/local/lib/perl5/5.10.1/perl/man/man3
> >> -Dman1dir=/usr/local/man/man1 
> >> -Dsitearch=/usr/local/lib/perl5/site_perl/5.10.1/mach
> >> -Dsitelib=/usr/local/lib/perl5/site_perl/5.10.1 -Dscriptdir=/usr/local/bin
> >> -Dsiteman3dir=/usr/local/lib/perl5/5.10.1/man/man3 
> >> -Dsiteman1dir=/usr/local/man/man1
> >> -Ui_malloc -Ui_iconv -Uinstallusrbinperl -Dcc=cc -Duseshrplib 
> >> -Dinc_version_list=none
> >> -Dccflags=-DAPPLLIB_EXP="/usr/local/lib/perl5/5.10.1/BSDPAN" -Doptimize=-g 
> >> -DDEBUGGING
> >> -Ud_dosuid -Ui_gdbm -Dusethreads=y -Dusemymalloc=n -Duse64bitint'
> >> threaded
>> Interesting. I have a perl 5.8.9, similiar config_args except for 
>> -Dusemymalloc=y and
>> without -Doptimize=-g, -DDEBUGGING. Fresh current, i386, compiled with gcc.
>> frozen-bubble run ok.
>> Do You run latest perl-sdl 2.2.6?
> Yes:
>> Did You rebuild it after upgrade to 5.10.1 perl version? 
> Yes.
>> Is game also crash without LD_PRELOAD=/usr/lib/libpthread.so?
> Yes, just the same.
I have upgraded perl to 5.10.1, but unfortunatelly could not run the game:
Graphicsrotate_bicubic: orig surface must be 32bpp (bytes per pixel = 1)
Perhaps because some time ago I have switched to ati and xf86-video-ati
from nvidia blob. Sigh.
Anyway, can You please downgrade perl-sdl to previous port version
(but keep p5-YAML dependency) and see if this help?


--
Adios
___
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"

Re: SDL, perl and frozen-bubble: core dumped

[Alex Kozlov]

On Fri, Mar 11, 2011 at 02:34:44PM +0300, Boris Samorodov wrote:
> On Fri, 11 Mar 2011 12:44:12 +0200 Alex Kozlov wrote:
>> On Fri, Mar 11, 2011 at 01:06:35PM +0300, Boris Samorodov wrote:
> >> I've got a core dump at clang compiled current. The game is starting,
> >> playing the music and coredumps right after displaying the menu:
>> Please show perl -V | grep -- -Dusethreads=y && echo threaded
> 
> Here it is:
> -
> % perl -V | grep -- -Dusethreads=y && echo threaded
> config_args='-sde -Dprefix=/usr/local 
> -Darchlib=/usr/local/lib/perl5/5.10.1/mach
> -Dprivlib=/usr/local/lib/perl5/5.10.1 
> -Dman3dir=/usr/local/lib/perl5/5.10.1/perl/man/man3
> -Dman1dir=/usr/local/man/man1 
> -Dsitearch=/usr/local/lib/perl5/site_perl/5.10.1/mach
> -Dsitelib=/usr/local/lib/perl5/site_perl/5.10.1 -Dscriptdir=/usr/local/bin
> -Dsiteman3dir=/usr/local/lib/perl5/5.10.1/man/man3 
> -Dsiteman1dir=/usr/local/man/man1
> -Ui_malloc -Ui_iconv -Uinstallusrbinperl -Dcc=cc -Duseshrplib 
> -Dinc_version_list=none
> -Dccflags=-DAPPLLIB_EXP="/usr/local/lib/perl5/5.10.1/BSDPAN" -Doptimize=-g 
> -DDEBUGGING
> -Ud_dosuid -Ui_gdbm -Dusethreads=y -Dusemymalloc=n -Duse64bitint'
> threaded
Interesting. I have a perl 5.8.9, similiar config_args except for 
-Dusemymalloc=y and
without -Doptimize=-g, -DDEBUGGING. Fresh current, i386, compiled with gcc.
frozen-bubble run ok.

Do You run latest perl-sdl 2.2.6?
Did You rebuild it after upgrade to 5.10.1 perl version? 
Is game also crash without LD_PRELOAD=/usr/lib/libpthread.so?


--
Adios
___
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"

Re: SDL, perl and frozen-bubble: core dumped

[Alex Kozlov]

On Fri, Mar 11, 2011 at 01:06:35PM +0300, Boris Samorodov wrote:
> I've got a core dump at clang compiled current. The game is starting,
> playing the music and coredumps right after displaying the menu:
Please show perl -V | grep -- -Dusethreads=y && echo threaded


--
Adios 
___
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"

Re: i keep *trying* to move from portupgrade to portmaster

[Alex Kozlov]

On 08/06/2010 00:24, Sandra Kachelmann wrote:
> I've been using ports-mgmt/portupgrade pretty much ever since it
> started to exist. Unfortunately portupgrade seems to be pretty much
> "abandonware" so I've been told to move on to portmaster. Despite the
> very long manpage I can't seem to be able to achieve the following
> thing with portmaster:
> $ portupgrade --batch -a
Try echo BATCH?=yes >>/etc/make.conf && portmaster --no-confirm -a


--
Adios
___
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"

Re: Problems with sysutils/screen (GNU Screen)

[Alex Kozlov]

On Fri, Jul 23, 2010 at 03:23:41PM -0400, Jim Trigg wrote:
> I've been having problems with GNU Screen on FreeBSD 8.x.  First, the
> TERMCAP environment variable as automatically set by screen causes
> things not to work. (vi says "cannot open terminal database", mutt
> says "no terminal database", etc.)  Second, when I put `eval tset -s`
> in .bashrc to reset the TERMCAP, curses-based programs work from
> command lines in open windows but don't work through "screen
> {command}" to launch them in a separate window -- the window flashes
> open and back closed.  /usr/local/bin/bash is my login shell.  This
> all still works in FreeBSD 7.
> 
> Any suggestions?
echo 'unset TERMCAP' >>~/.profile
And try tmux.


--
Adios
___
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"

Re: DosBox upgrade failed.

[Alex Kozlov]

On Sun, May 30, 2010 at 10:58:42AM +0200, David Marec wrote:
> I got the following issue, upgrading Dosbox to the 0.74 release:
> 
> ===
> Making all in core_dynrec
> g++44 -DHAVE_CONFIG_H -I. -I../..   -I../../include -I/usr/local/include -
> I/usr/local/include/SDL -I/usr/local/include -D_GNU_SOURCE=1 -D_REENTRANT  
> -O2 
> -pipe -march=native -fno-strict-aliasing -MT callback.o -MD -MP -MF 
> .deps/callback.Tpo -c -o callback.o callback.cpp
> mv -f .deps/callback.Tpo .deps/callback.Po
> g++44 -DHAVE_CONFIG_H -I. -I../..   -I../../include -I/usr/local/include -
> I/usr/local/include/SDL -I/usr/local/include -D_GNU_SOURCE=1 -D_REENTRANT  
> -O2 
> -pipe -march=native -fno-strict-aliasing -MT cpu.o -MD -MP -MF .deps/cpu.Tpo -
> c -o cpu.o cpu.cpp
> In file included from cpu.cpp:29:
> ../../include/setup.h:247: error: 'FILE' has not been declared
> ../../include/setup.h:280: error: 'FILE' has not been declared
> ../../include/setup.h:315: error: 'FILE' has not been declared
> *** Error code 1
> Any idea to solve this ?
Try to add 'include ', if it's not help, use base gcc (4.2.1)
instead of lang/gcc44.


--
Adios
___
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"

Re: [HEADS UP] Experimental 3D HW accel support for Radeon HD 2xxx, 3xxx and 4xxx, 2nd!

[Alex Kozlov]

On Tue, Dec 22, 2009 at 11:38:50PM -0600, Robert Noland wrote:
> On Wed, 2009-12-23 at 07:31 +0200, Alex Kozlov wrote:
> > On Wed, Dec 23, 2009 at 02:03:15AM +0900, Norikatsu Shigemura wrote:
> > > On Tue, 22 Dec 2009 00:26:38 -0600 Robert Noland  
> > > wrote:
> > > > As much as I don't want to, I need to request a repo copy of libdrm in
> > > > order to keep nouveau working...  The bits needed for r600 were added
> > > > just after 2.4.12 and the bits that broke nouveau were just before
> > > > 2.4.13...
> > > 
> > >   Ah, I just see! ABI breakage is building issue, I confirmed:
> > > 
> > >   I think simple-fully xf86-video-nouveau updating at the same
> > >   time.  Please see also attached patch.  I confirmed that
> > >   compile is OK.  But I don't have any GeForce video cards.
> > >   So I don't know any problems of updating it in real.
> > > 
> > >   And do you have any recommendation of GeForce? e.g. 9800GTX,
> > >   GT260, ...  I'll get one and test.  I'm interested in Cuda
> > >   and nvidia binary driver, too.
> > > 
> > > P.S. libdrm was update to 2.4.17, so I'll update...
> > I just tested libdrm 2.4.17 with --enable-radeon-experimental-api 
> > and mesalib git master. It's work quite good. Well, it worked
> > quite good before 
> 
> I've said it before, but I'll repeat... libdrm_radeon serves no purpose
> on FreeBSD and may cause problems.  It is only used by TTM/KMS enabled
> drivers on linux.  If it ever becomes useful... I'll enable it in the
> port.
Sorry. I only mean that libradeon is a harmless at the moment.

Could You please let us know rough roadmap for freebsd kernel drm? 


> > "Merge branch 'glsl-pp-rework-2'" (e195eab9093d2a6cf55a42b2e7789c9a381b778)
> > but this is separate matter.
> > So may be enabling libdrm_radeon is not such a bad idea.


--
Adios
___
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"

Re: [HEADS UP] Experimental 3D HW accel support for Radeon HD 2xxx, 3xxx and 4xxx, 2nd!

[Alex Kozlov]

On Wed, Dec 23, 2009 at 02:03:15AM +0900, Norikatsu Shigemura wrote:
> On Tue, 22 Dec 2009 00:26:38 -0600 Robert Noland  wrote:
> > As much as I don't want to, I need to request a repo copy of libdrm in
> > order to keep nouveau working...  The bits needed for r600 were added
> > just after 2.4.12 and the bits that broke nouveau were just before
> > 2.4.13...
> 
>   Ah, I just see! ABI breakage is building issue, I confirmed:
> 
>   I think simple-fully xf86-video-nouveau updating at the same
>   time.  Please see also attached patch.  I confirmed that
>   compile is OK.  But I don't have any GeForce video cards.
>   So I don't know any problems of updating it in real.
> 
>   And do you have any recommendation of GeForce? e.g. 9800GTX,
>   GT260, ...  I'll get one and test.  I'm interested in Cuda
>   and nvidia binary driver, too.
> 
> P.S. libdrm was update to 2.4.17, so I'll update...
I just tested libdrm 2.4.17 with --enable-radeon-experimental-api 
and mesalib git master. It's work quite good. Well, it worked
quite good before 
"Merge branch 'glsl-pp-rework-2'" (e195eab9093d2a6cf55a42b2e7789c9a381b778)
but this is separate matter.

So may be enabling libdrm_radeon is not such a bad idea.


--
Adios
___
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"

Re: [HEADS UP] Experimental 3D HW accel support for Radeon HD 2xxx, 3xxx and 4xxx.

[Alex Kozlov]

On Sat, Dec 05, 2009 at 10:42:43AM +0900, Norikatsu Shigemura wrote:
> Hi Radeon HD 2xxx, 3xxx and 4xxx users!
> 
>   I'm ready to update ports related Mesa3D to 7.6 base, graphics/dri,
>   graphics/libGL*, graphics/libglut, graphics/mesa-demos and
>   graphics/libdrm.  Please see also my attached patch file.  I'll
>   update these as soon as tomorrow.
> 
>   Mesa3D 7.6 supports experimental r600 driver, as known as AMD
>   R6xx/R7xx architecture.  I confirmed that it's good works, but
>   buggy on my Radeon HD 4850 environment with 9-current/amd64 and
>   xf86-video-radeonhd-devel.  Please see also [I known problem]
>   section.
I use similiar setup(but with mesa git master) for more than a month
without a problem. HD 3650 AGP. glxgear, other demos and even some old
games in wine like deusex work fine. 


--
Adios
___
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"

Re: Port of "service" command

[Alex Kozlov]

On Tue, Jun 09, 2009 at 12:30:44PM -0700, Doug Barton wrote:
> Kevin Downey wrote:
>> I have a similar shell function I am rather fond of:
>> 
>> rc(){
>> find /etc/rc.d/"$1" /usr/local/etc/rc.d/"$1" -exec sudo {} `echo
>> "$*"|cut -f 2- -d \ ` \;
>> }
> 
> Wow, that's painful. :) The only reason you don't notice how painful
> is because those two directories have only a few files. Much much more
> efficient would be something like:
> 
> rc () {
>   local script=$1
>   shift
> 
>   if [ -x "/etc/rc.d/$script" ]; then
>   /etc/rc.d/$script $*
>   elif [ -x "/usr/local/etc/rc.d/$script" ]; then
>   /usr/local/etc/rc.d/$script $*
>   else
>   echo "$script does not exist in /etc/rc.d or"
>   echo "/usr/local/etc/rc.d"
>   return 1
>   fi
> }

#!/bin/sh

name=$1
cmd=$2

if [ -z "${name}" -o -z "${cmd}" ]; then
echo ${0##*/} service_name command
exit 3
fi

. /etc/rc.subr

load_rc_config ${name}

for dir in /etc/rc.d ${local_startup}; do
if [ -r "${dir}/${name}" ]; then
run_rc_script "${dir}/${name}" ${cmd}
exit 0
fi

if [ -r "${dir}/${name}.sh" ]; then 
run_rc_script "${dir}/${name}.sh" ${cmd}
exit 0
fi  
done

echo "service '${name}' not found"
exit 2


Most useful with shell completion.


--
Adios
___
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"

perl-threaded

[Alex Kozlov]

On Wed, Mar 18, 2009 at 09:31:18PM +0100, Cezary Morga wrote:
> I've just noticed in some of the ports a dependency of 
> perl-threaded-5.8.9_2 and I'm wondering how is it resolved by the port 
> building system?
> 
> I've got one port that requires threaded Perl and I worked around it to 
> check whether thread support is compiled and if not tell user to 
> recompile Perl with threads, but maybe that's unnecessary?
You can check ports/devel/p5-SDL/Makefile for reference.


--
Adios
___
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"

Re: exim 4.69 won't build

[Alex Kozlov]

On Sun, Sep 28, 2008 at 10:05:49AM -0700, Mark Foster wrote:
> I'm getting this error when trying to compile (via make) the mail/exim 
> port (v4.69).
> ...
> cc -o exim
> lookups/lookups.a(nis.o)(.text+0x33): In function `nis0_find':
> : undefined reference to `yp_match'
> lookups/lookups.a(nis.o)(.text+0xa0): In function `nis_find':
> : undefined reference to `yp_match'
> lookups/lookups.a(nis.o)(.text+0xed): In function `nis_open':
> : undefined reference to `yp_get_default_domain'
> *** Error code 1
> 
> I'd use send-pr to report this, but exim is broken, so a catch-22.
Remove NO_NIS/WITHOUT_NIS from make.conf/src.conf

or add this to make.conf:
.if ${.CURDIR:N*/ports/mail/exim} == ""
WITHOUT_PERL=yes
WITHOUT_NIS=yes
.endif


--
Adios
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Standardize NO_CCACHE flag and ccache definitions

[Alex Kozlov]

On Sat, Jun 21, 2008 at 01:32:20AM +0100, RW wrote:
> On Wed, 18 Jun 2008 23:27:16 +0200
> Martin Tournoij <[EMAIL PROTECTED]> wrote:
> 
> 
> > There are some ports which refuse to compile with ccache, these all
> > seem to be projects which use scons, unlike make, scons does not copy
> > the user's environment automatically, and the required environment
> > variables for ccache (like CCACHE_DIR) aren't present, which leads to
> > build failure, an example is games/freera.
> > 
> > I'm not that familiar with scons, and what exactly the "proper way" is
> > to handle this sort of stuff in scons, 
> 
> I don't have any experience with scons, but I did used to use cons.
> IIRC cons expects to do the caching itself. Since it already generates a
> hash that can be used to label the correct object file, it pretty much
> comes for free and running ccache would just duplicate the overheads. I
> think it's probable that there isn't a "proper way".
>From porter's handbook:

To make third party SConstruct respect everything that is passed to SCons
in SCONS_ENV (that is, most importantly, CC/CXX/CFLAGS/CXXFLAGS), patch
the SConstruct so build Environment is constructed like this:
env = Environment(**ARGUMENTS)

It may be then modified with env.Append and env.Replace.


--
Adios
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Standardize NO_CCACHE flag and ccache definitions

[Alex Kozlov]

On Wed, Jun 18, 2008 at 07:05:36PM +0100, RW wrote:
> On Wed, 18 Jun 2008 20:23:52 +0300
> Alex Kozlov <[EMAIL PROTECTED]> wrote:
> > This is not luck. To think more about this, CCACHE_HASH_COMPILER
> > and CCACHE_NOHASH_SIZE_MTIME is two method for the same.
> > hash size and mtime is lightweight and CCACHE_HASH_COMPILER
> > is more heavy.
> It's negligible, it added a few seconds to a build of Firefox,
> and I had to build it ten times to determine that because the
> build-to-build variations are much greater. 
I check this.

> > But in case of buildworld CCACHE_HASH_COMPILER is still not necessary,
> > CCACHE_NOHASH_SIZE_MTIME is enough.
> It depends what you want to achieve, the object of ccache is to
> cache compiler outputs where the results are identical to a fresh
> build (subject to possible minor exceptions like source file paths). If
> you don't detect compiler updates then you can no longer say that's
> true.
In typical case check for size and mtime is enough.
For buildworld We can disable even it, because compiler version
very rare change in RELENG_X lifetime.

In case of tinderbox farm I'm not so sure, if jails don't share
.ccache it probably relatively safe. This is need checking.
If overhead for CCACHE_HASH_COMPILER not big, may be worth turn
it on. Also need testing.

For too smart for it own good ports We can add to /etc/make.conf
something like this:
.if ${.CURDIR:N*/ports/devel/cmake} !="" && ...
CC = ccache
CXX = ccache
.endif

> If you use CCACHE_NOHASH_SIZE_MTIME then you are accepting object files
> produced by mixture of, arbitrarily old, versions of the compiler. If a
> new compiler version brings in better code generation, I'd rather pick
> it up.
> 
> CCACHE_HASH_COMPILER is a good compromise IMO, because it will detect
> changes in the driver, without being sensitive to minor world rebuilds.
> You still need to watch for security updates to GCC because in
> principle they might not affect the drivers, that's rare though.


--
Adios
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Standardize NO_CCACHE flag and ccache definitions

[Alex Kozlov]

On Wed, Jun 18, 2008 at 06:44:36PM +0200, Alex Dupre wrote:
>> Problem in make buildworld case is not compiler name.
> hash_file() doesn't hash the file name :-)
Yes, sorry. s/name/identity/. In other words this check to make
sure that obj was created the same compiler.

> You are lucky that CCACHE_HASH_COMPILER is checked before
> CCACHE_NOHASH_SIZE_MTIME.
This is not luck. To think more about this, CCACHE_HASH_COMPILER
and hash size and mtime is two method for the same.
Former is lightweight and CCACHE_HASH_COMPILER is more heavy.
But in case of buildworld CCACHE_HASH_COMPILER is still not necessary,
CCACHE_NOHASH_SIZE_MTIME is enough.


--
Adios
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Standardize NO_CCACHE flag and ccache definitions

[Alex Kozlov]

On Wed, Jun 18, 2008 at 06:44:36PM +0200, Alex Dupre wrote:
> Alex Kozlov wrote:
> > Problem in make buildworld case is not compiler name.
> hash_file() doesn't hash the file name :-)
Yes, sorry. s/name/identity/. In other world this check to make
sure that obj was created the same compiler.

> You are lucky that CCACHE_HASH_COMPILER is checked before
> CCACHE_NOHASH_SIZE_MTIME.
This is not luck. To think more about this, CCACHE_HASH_COMPILER
and CCACHE_NOHASH_SIZE_MTIME is two method for the same.
hash size and mtime is lightweight and CCACHE_HASH_COMPILER
is more heavy.
But in case of buildworld CCACHE_HASH_COMPILER is still not necessary,
CCACHE_NOHASH_SIZE_MTIME is enough.


--
Adios
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Standardize NO_CCACHE flag and ccache definitions

[Alex Kozlov]

On Wed, Jun 18, 2008 at 05:48:38PM +0200, Alex Dupre wrote:
> Alex Kozlov ha scritto:
> >> It's necessary if you don't want to use ccache only for 1% of the 
> >> buildworld process.
> > I use CCACHE_NOHASH_SIZE_MTIME:
> 
> "It's not necessary to use CCACHE_HASH_COMPILER" != "I use 
> CCACHE_NOHASH_SIZE_MTIME, so every compiler I use I will get always the 
> same result."
Problem in make buildworld case is not compiler name.
Problem is that compiler rebuild itself and mtime alway different.
So I'm use switch exactly for this case and not depend on side effects
CCACHE_HASH_COMPILER. Also later is undocumented.


--
Adios
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Standardize NO_CCACHE flag and ccache definitions

[Alex Kozlov]

On Wed, Jun 18, 2008 at 05:05:42PM +0200, Alex Dupre wrote:
> Alex Kozlov ha scritto:
> > Don't use it for building ports. Actualy it's not necessary even for
> > make buildworld.
> 
> It's necessary if you don't want to use ccache only for 1% of the 
> buildworld process.
I use CCACHE_NOHASH_SIZE_MTIME:

if (getenv("CCACHE_HASH_COMPILER")) {
hash_file(args->argv[0]);
} else if (!getenv("CCACHE_NOHASH_SIZE_MTIME")) {
hash_int(st.st_size);
hash_int(st.st_mtime);
}


--
Adios
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Standardize NO_CCACHE flag and ccache definitions

[Alex Kozlov]

On Wed, Jun 18, 2008 at 11:16:42PM +1000, Edwin Groothuis wrote:
> On Wed, Jun 18, 2008 at 03:01:58PM +0200, Alex Dupre wrote:
> > Edwin Groothuis ha scritto:
> > >Recently I've started to use devel/ccache again (sometimes it takes
> > >a while before you understand how it works) and it works pretty
> > >well, except for some ports which can't be build with it. For example
> > >devel/cmake.
> > 
> > I use ccache everywhere (world and ports) and I never found a port that 
> > doesn't compile with it (I have cmake, too).
> 
> When building devel/cmake in a jail with ccache enabled it doesn't get 
> further than:
> 
> ===>  Configuring for cmake-2.6.0
> -
> CMake 2.6-0, Copyright (c) 2007 Kitware, Inc., Insight Consortium
> C compiler on this system is: /usr/local/libexec/ccache/world-cc -O2 
> -fno-strict-aliasing -pipe 
> C++ compiler on this system is: /usr/local/libexec/ccache/world-c++ -O2 
> -fno-strict-aliasing -pipe
> [...]
> CMake has bootstrapped.  Now run make.
> ===>  Building for cmake-2.6.0
> Scanning dependencies of target cmsys
> [  0%] Building C object Source/kwsys/CMakeFiles/cmsys.dir/ProcessUNIX.o
> [  0%] Building C object Source/kwsys/CMakeFiles/cmsys.dir/Base64.o
> [  0%] Building C object Source/kwsys/CMakeFiles/cmsys.dir/MD5.o
> [  1%] Building C object Source/kwsys/CMakeFiles/cmsys.dir/Terminal.o
> [  1%] Building C object Source/kwsys/CMakeFiles/cmsys.dir/System.o
> [  1%] Building C object Source/kwsys/CMakeFiles/cmsys.dir/String.o
> [  2%] Building CXX object Source/kwsys/CMakeFiles/cmsys.dir/Directory.o
> [  2%] Building CXX object Source/kwsys/CMakeFiles/cmsys.dir/DynamicLoader.o
> [  2%] Building CXX object Source/kwsys/CMakeFiles/cmsys.dir/Glob.o
> [  3%] Building CXX object 
> Source/kwsys/CMakeFiles/cmsys.dir/RegularExpression.o
> [  3%] Building CXX object Source/kwsys/CMakeFiles/cmsys.dir/SystemTools.o
> [  3%] Building CXX object 
> Source/kwsys/CMakeFiles/cmsys.dir/CommandLineArguments.o
> [  4%] Building CXX object Source/kwsys/CMakeFiles/cmsys.dir/Registry.o
> [  4%] Building CXX object Source/kwsys/CMakeFiles/cmsys.dir/IOStream.o
> [  4%] Building CXX object 
> Source/kwsys/CMakeFiles/cmsys.dir/SystemInformation.o
> Linking CXX static library libcmsys.a
> Error running link command: No such file or directory
> *** Error code 2
> 
> This happens with ccache, without ccache it doesn't.
> 
> There are a couple of others which I can't recall right now.
/usr/local/libexec/ccache/world-c++ sets CCACHE_HASH_COMPILER
Don't use it for building ports. Actualy it's not necessary even for
make buildworld.


--
Adios
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: INDEX build optimizations - please review

[Alex Kozlov]

On Wed, Jun 11, 2008 at 10:22:18AM -0700, Doug Barton wrote:
> Alex Kozlov wrote:
> 
> > Good idea. I also do something like that [1]. But before we can use this
> > method, we have to fix ports with bad pkg-descr:
> 
> Yeah, in a brief glance at Kris' sed routines I would think at least 
> some of this work would have to be done no matter what (and it should be 
> done anyway), so thank you for your thorough examination of this. :)
> 
> Since you were kind enough to do the legwork, I'll be glad to commit the 
> fixes if no other committer picks up the ball.
Was glad to help.

p.s. Played with more sophisticated parser and found some more broken
pkg-descr, can You please fix it too? Thanks.

WWW: is not the first word in a line:
chinese/pine4
devel/ptmalloc
emulators/its
emulators/klh10
japanese/Wnn6


--
Adios
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: INDEX build optimizations - please review

[Alex Kozlov]

On Tue, Jun 10, 2008 at 04:49:18PM -0700, Doug Barton wrote:
> Kris Kennaway wrote:
> 
> > The new 'make describe' target runs entirely using shell 
> > builtins apart from the need to sed pkg-descr to extract the WWW [2] 
> 
> > [2] Actually I am not happy with this but couldn't think of a way to do 
> > it better.  Having to fork the subshell costs about 60 seconds of system 
> > time and 10 of wall time.
> 
> Here's one way to do it. This is quick and dirty and I haven't 
> benchmarked it, but I imagine it would be faster.
> 
> while read one two discard; do
>   case "$one" in
>   WWW:)   echo one: $one two: $two
>   case "$two" in
>   http://*) echo WWW= $two ;;
>   *) echo WWW=  http://$two ;;
>   esac
>   break
>   ;;
>   esac
> done < pkg-descr
> 
> I did test this briefly and it pulls out the right values for
> variables with and without http://.
Good idea. I also do something like that [1]. But before we can use this
method, we have to fix ports with bad pkg-descr:

Don't have \n in WWW: line
 databases/powerarchitect
 graphics/picturebook

Have CRLF line terminators:
 devel/p5-Tie-Restore
 www/knowledgekit
 www/squishdot
 www/znavigator
 www/zope-cmfforum

Have http:/ instead of http://
 security/shimmer

Don't have protocol prefix(optional):
 net/pdb
 sysutils/iograph


[1] (Incremental to kris@ patch.):

Index: Mk/bsd.port.mk
@@ -5290,16 +5290,18 @@
 _RUN_DEPENDS=${RUN_DEPENDS:C/^[^ :]+:([^ :]+)(:[^ :]+)?/\1/:O:u} 
${_LIB_DEPENDS}
 .if exists(${DESCR})
 _DESCR=${DESCR}
+_WWW=while read line; do set -- $${line}; case $$1 in WWW:) case $$2 \
+in http://*|https://*|ftp://*) ${ECHO_CMD} $$2 ;; *) \
+${ECHO_CMD} "http://$$2"; ;; esac; break ;; esac; done < ${DESCR}
 .else
 _DESCR=/dev/null
+_WWW=
 .endif
 
 describe:
-   @${ECHO_CMD} -n "${PKGNAME}|${.CURDIR}|${PREFIX}|"; \
-   ${ECHO_CMD} -n ${COMMENT:Q}; \
-   ${ECHO_CMD} -n 
"|${_DESCR}|${MAINTAINER}|${CATEGORIES}|${_EXTRACT_DEPENDS}|${_PATCH_DEPENDS}|${_FETCH_DEPENDS}|${_BUILD_DEPENDS:O:u}|${_RUN_DEPENDS:O:u}|";
 \
-   set "" $$(sed -E -e '/^WWW:[[:blank:]]+/!d' -e 
's,^WWW:[[:blank:]]+([[:print:]]+).*$$,\1,' ${_DESCR}); \
-   echo $$2
+   @${ECHO_CMD} 
"${PKGNAME}|${.CURDIR}|${PREFIX}|"${COMMENT:Q}"|${_DESCR}|${MAINTAINER}"\
+   
"|${CATEGORIES}|${_EXTRACT_DEPENDS}|${_PATCH_DEPENDS}|${_FETCH_DEPENDS}"\
+   "|${_BUILD_DEPENDS:O:u}|${_RUN_DEPENDS:O:u}|"$$( ${_WWW})
 .endif
 # | (read site && ${ECHO_CMD} $${site}) || ${ECHO_CMD}
 #  sed -E -e '/^WWW:/!d' -e 's,^WWW:.*(http[:print:]*),\1,' ${_DESCR} | 
(read site && ${ECHO_CMD} $${site})


--
Adios
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: INDEX build optimizations - please review

[Alex Kozlov]

On Tue, Jun 10, 2008 at 11:52:01PM +0200, Kris Kennaway wrote:
> Alex Kozlov wrote:
> > On Tue, Jun 10, 2008 at 06:45:32PM +0200, Kris Kennaway wrote:
> >> Please review and test the following patches that optimize port INDEX 
> >> builds (and as a side-effect, other recursive tree traversals).  I am 
> >> particularly interested in a comparison between old and new indexes 
> >> built locally: the only diff should be in audio/festvox-hvs [1].
> > Work on RELENG_6 only after this patch (maybe good candidate for MFC):
> 
> Crap!  I need :u!  Without it the duplicate removal will have to be 
> pushed into the perl script that collates the output, which means that 
> Colin's portsnap script may be affected.
> 
> The patch definitely should be MFCed though.  Who committed it 
> originally to HEAD?
var.c Revision 1.161 Sat Apr 8 06:59:54 2006 UTC (2 years, 2 months ago) by fjoe


--
Adios
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: INDEX build optimizations - please review

[Alex Kozlov]

On Tue, Jun 10, 2008 at 06:45:32PM +0200, Kris Kennaway wrote:
> Please review and test the following patches that optimize port INDEX 
> builds (and as a side-effect, other recursive tree traversals).  I am 
> particularly interested in a comparison between old and new indexes 
> built locally: the only diff should be in audio/festvox-hvs [1].
Work on RELENG_6 only after this patch (maybe good candidate for MFC):


Index: usr.bin/make/var.c
@@ -1232,6 +1232,41 @@
 }

 /**
+ * Remove adjacent duplicate words.
+ *
+ * Results:
+ * A string containing the resulting words.
+ */
+static char *  
+VarUniq(const char *str)
+{
+   ArgArrayaa;
+   Buffer  *buf;   /* Buffer for new string */
+   int i, j;
+
+   buf = Buf_Init(0);
+   brk_string(&aa, str, FALSE);
+
+   if (aa.argc > 2) {
+   for (j = 1, i = 2; i < aa.argc; i++) {
+   if (strcmp(aa.argv[i], aa.argv[j]) != 0 && (++j != i))
+   aa.argv[j] = aa.argv[i];
+   }
+   aa.argc = j + 1;
+   }
+
+   for (i = 1; i < aa.argc; i++) {
+   Buf_AddBytes(buf, strlen(aa.argv[i]), (Byte *)aa.argv[i]);
+   if (i != aa.argc - 1)
+   Buf_AddByte(buf, ' ');
+   }
+   Buf_AddByte(buf, '\0');
+
+   ArgArray_Done(&aa);
+   return (Buf_Peel(buf));
+}
+
+/**
  * Pass through the tstr looking for 1) escaped delimiters,
  * '$'s and backslashes (place the escaped character in
  * uninterpreted) and 2) unescaped $'s that aren't before
@@ -1681,6 +1716,7 @@
  * the invocation.
  * :U  Converts variable to upper-case.
  * :L  Converts variable to lower-case.
+ * :u  ("uniq") Remove adjacent duplicate words.
  *
  * XXXHB update this comment or remove it and point to the man page.
  */
@@ -1793,6 +1829,10 @@
newStr = VarModify(value, VarRoot, NULL);
vp->ptr++;
break;
+   case 'u':
+   newStr = VarUniq(value);
+   vp->ptr++;
+   break;
default:
newStr = sysVvarsub(vp, startc, v, value);
break;


--
Adios
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

porting of SVN-only software

[Alex Kozlov]

On Fri, May 16, 2008 at 09:54:09PM +0300, Andriy Gapon wrote:
> 
> Suppose there is a project that does not produce any official snapshots or 
> releases of its source-code, keeps all sources in SVN and the best it does 
> - declares a certain revision as stable or something similar.
> What would be the best way to create a FreeBSD port for such software?
> Any examples?
You may find multimedia/flv2mpeg4 useful. 

> Thank you!


--
Adios
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: net-im/openfire port related question.

[Alex Kozlov]

On Wed, Feb 13, 2008 at 06:50:45PM +0200, Nikolay Pavlov wrote:
> Hello all. I am a maintainer of the net-im/openfire port. I have a report 
> from Dmitri Frolov <[EMAIL PROTECTED]> that openfire uses the same uid 
> as security/stunnel port. Could someone please suggest me as how i can 
> resolve this situation?
Change uid/gid in net-im/openfire/pkg-install. Add new values to
/usr/ports/UIDs, /usr/ports/GIDs to prevent this situation in the
future.


--
Adios
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Proposition: make x11/nvidia-driver independent of misc/compat5x

[Alex Kozlov]

On Sat, Oct 27, 2007 at 10:53:30PM -0200, Carlos A. M. dos Santos wrote:

> > > [/usr/local/lib/xorg/modules/libwfb.so]
> > > libm.so.3   libm.so.4
> > > librpcsvc.so.2  librpcsvc.so.3
> >
> > If I specify the full path the mapping does not work. The X server
> > still loades, but gives me the following message:
> >
> >  dlopen: Shared object "libm.so.3" not found, required by "libwfb.so"
Sorry. I use nvidia-driver-96xx, so I was not be able to test libwfb case.

> ... so my patch now becomes the one provided below. Extract it piping
> this message to
> 
>  b64decode -o /dev/stdout | gzip -d > nvidia-driver.diff
> 
> CC to the port maintainer now. I suppose that he subscribes the list
> but, well, just in case.
Also, I think that libmap trick is good for local hack, but must not be
applied by default in port. Print libmap suggestion from pre-everything
will be enough.


--
Adios
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Proposition: make x11/nvidia-driver independent of misc/compat5x

[Alex Kozlov]

On Sat, Oct 27, 2007 at 11:33:46AM -0200, Carlos A. M. dos Santos wrote:
> Hello,
> 
> Using the patch below it is possible to make x11/nvidia-driver
> independent of misc/compat5x, by means of some library mapping. I did
> this successfuly on 6.x but still did not test on 7.x. I would like to
> hear some comments before submitting a PR with a change request.
I think this is more correct variant:

$cat /etc/libmap.conf
#nvidia-driver
[/usr/local/lib/libGL.so.1]
libm.so.3   libm.so.4

[/usr/local/lib/libXvMCNVIDIA.so.1]
libc.so.5   libc.so.6

[/usr/local/lib/libXvMCNVIDIA_dynamic.so.1]
libc.so.5   libc.so.6

[/usr/local/lib/libnvidia-cfg.so.1]
libm.so.3   libm.so.4

[/usr/local/lib/xorg/modules/libwfb.so]
libm.so.3   libm.so.4
librpcsvc.so.2  librpcsvc.so.3


--
Adios
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"