Re[2]: Linux Compatibility version of libXau

2008-06-10 Thread Геннадий Максимович Филиппов
ХЗ
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]


converters/libiconv build error

2008-06-10 Thread Henk van Oers


On a small FreeBSD 6.3 system (Pentium I, 120 MHz, 32 MB)
i have postfix running, a bit of perl and ... bash

I did an upgrade after reading:
q
20080605:
  AFFECTS: users of devel/gettext (ie: YOU)
  AUTHOR: [EMAIL PROTECTED]

  As a result of the upgrade to gettext-0.17, the shared library version
  of libintl has changed, so you will need to rebuild all ports that
  depend on gettext:

  # portupgrade -rf gettext
  # portmaster -r gettext\*

  Given the scope and sheer number of dependent ports, it may be more
  advisable to simply blow away all existing install ports (after
  keeping any local configuration changes), and rebuilding from scratch.
/q

Even with a hand full of gettext dependencies, normal upgrade did not
work, so i deleted all related ports and started rebuilding from scratch.

For bash i need converters/libiconv but is stops with:
[...]
config.status: creating po/Makefile
./configure.lineno: 40477: Syntax error: Unterminated quoted string
===  Script configure failed unexpectedly.
Please run the gnomelogalyzer, available from
http://www.freebsd.org/gnome/gnomelogalyzer.sh;, which will diagnose the
problem and suggest a solution. If - and only if - the gnomelogalyzer 
cannot

solve the problem, report the build failure to the FreeBSD GNOME team at
[EMAIL PROTECTED], and attach (a)
/usr/ports/converters/libiconv/work/libiconv-1.11/config.log, (b) the 
output
of the failed make command, and (c) the gnomelogalyzer output. Also, it 
might
be a good idea to provide an overview of all packages installed on your 
system

(i.e. an `ls /var/db/pkg`). Put your attachment up on any website,
copy-and-paste into http://freebsd-gnome.pastebin.com, or use send-pr(1) 
with

the attachment. Try to avoid sending any attachments to the mailing list
([EMAIL PROTECTED]), because attachments sent to FreeBSD mailing lists are
usually discarded by the mailing list software.
*** Error code 1

Stop in /usr/ports/converters/libiconv.
*** Error code 1
---

Mmmm, ok, run gnomelogalyzer.sh on the logfile:

q
The cause of your build failure is not known to gnomelogalyzer.sh.  Before
e-mailing the build log to the FreeBSD GNOME team at 
[EMAIL PROTECTED],

TRY EACH OF THE FOLLOWING:

  * If you are generating your own logfile, make sure to generate it with
something similar to:
  make 21 | tee /path/to/logfile (sh/bash/ksh/zsh) or
  make | tee /path/to/logfile (csh/tcsh)
* Make sure your cvsup(1) configuration file specifies the 
'ports-all'

  collection
* Run cvsup(1) and attempt the build again
* Check /usr/ports/UPDATING for information pertinent to your 
build

  failure
* 99% of the commonly reported build failures can be solved by
  running portupgrade -a
* Read the FAQs at http://www.FreeBSD.org/gnome/
* Search the archives of [EMAIL PROTECTED]  Archives can 
be

  searched at http://www.freebsd.org/gnome/index.html#search

If you have not performed each of the above suggestions, don't bother 
asking
for help.  The chances are good that you'll simply be told to perform one 
of

the aforementioned steps.
/q

I did re-portsnap, portupgrade -a has nothing to do.
FAQ's and archive did not help.
I want my bash back, but it needs iconv

NB the output of 
/usr/ports/converters/libiconv/work/libiconv-1.11/config.log

is:
[]
#define VOID_UNSETENV 1
#define HAVE__BOOL 1
#define HAVE_STDBOOL_H 1
#define HAVE_STRERROR 1
#define HAVE_READLINK 1

configure: exit 2

Do you need the whole file?

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


FreeBSD Port: squid_radius_auth-1.0.8

2008-06-10 Thread Verbeek, Maarten
Hi,
 
The 1.0.8 version is currently out of date and contains a bug.
could this be updated to the current version if you are still
maintaining the code?
 
thnx
 
Maarten Verbeek 

ORDINA Belgium 
 
Contact Details
B-3001 Heverlee, Interleuvenlaan 15H
B-3560 Lummen, Bosstraat 52/2
B-9820 Merelbeke, Guldensporenlaan 84/I
B-2627 Schelle (Antwerpen), Boomsesteenweg 28


@[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]   
www.ordina.be http://www.ordina.be/   

 
Email Disclaimer

The information contained in or with this email, originating from
Ordina, is confidential and intended solely for the addressee. If this
email has been received in error the receiver is kindly asked to contact
the sender via email or telephone. Revelation, reproduction,
distribution and/or forwarding of the information contained to third
parties is not permitted. Ordina is not responsible for the correct and
complete transference of the content of any transmitted email, nor for
the timely reception thereof, nor for the correctness of the content. In
no case is Ordina liable for any damage, in any form, which may arise as
a direct or indirect consequence of acting and/or neglecting and/or
deciding anything based wholly or partly on this email. On all
activities and offers of Ordina, and in all agreements of which they are
directly or indirectly a party, the General Terms and Conditions apply,
even if not included. A copy of these Terms and Conditions will be send
to you free of charge on request.

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


Re: ports/37375: Test bug report (please ignore)

2008-06-10 Thread edwin
Synopsis: Test bug report (please ignore)

State-Changed-From-To: closed-Open
State-Changed-By: edwin
State-Changed-When: Tue Jun 10 12:59:37 UTC 2008
State-Changed-Why: 
tracing issue with edit-pr

http://www.freebsd.org/cgi/query-pr.cgi?pr=37375
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ports/37375: Test bug report (please ignore)

2008-06-10 Thread edwin
Synopsis: Test bug report (please ignore)

State-Changed-From-To: Open-open
State-Changed-By: edwin
State-Changed-When: Tue Jun 10 13:00:14 UTC 2008
State-Changed-Why: 
Fix capitalization

http://www.freebsd.org/cgi/query-pr.cgi?pr=37375
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ports/37375: Test bug report (please ignore)

2008-06-10 Thread edwin
Synopsis: Test bug report (please ignore)

State-Changed-From-To: open-closed
State-Changed-By: edwin
State-Changed-When: Tue Jun 10 13:00:36 UTC 2008
State-Changed-Why: 
Trace edit-pr issue

http://www.freebsd.org/cgi/query-pr.cgi?pr=37375
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ports/37375: Test bug report (please ignore)

2008-06-10 Thread edwin
Synopsis: Test bug report (please ignore)

Responsible-Changed-From-To: freebsd-ports-edwin
Responsible-Changed-By: edwin
Responsible-Changed-When: Tue Jun 10 13:00:49 UTC 2008
Responsible-Changed-Why: 
Chase edit-pr issue

http://www.freebsd.org/cgi/query-pr.cgi?pr=37375
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]


FreeBSD Port: nntpcache-3.0.2_6

2008-06-10 Thread Reinhard Haller
Hi,

I've problems to get nntpcache working on amd64 architecture. Are there
known issues or suggestions to get it working.

The original domain (nntpcache.org/com) is no longer allocated, so where can
I get any informations?

Thanks
Reinhard Haller

- 
Dipl. Inform. Reinhard Haller
INTERACTIVE Computer Systems GmbH
Gesellschaft für Systemtechnik

Hermann-Hesse-Str. 5
85551 Kirchheim b. München

Tel.: 089/904885-0
Mob.: 0171/8022551
Fax: 089/904885-22

mailto: [EMAIL PROTECTED]

Angaben gemäß EHUG:
Geschäftsführer: Reinhard Haller
eingetragen: Amtsgericht München, HRB 70987
USt-ID: DE129385991


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


Re: FreeBSD Port: squid_radius_auth-1.0.8

2008-06-10 Thread Wesley Shields
On Tue, Jun 10, 2008 at 01:28:05PM +0200, Verbeek, Maarten wrote:
 Hi,
  
 The 1.0.8 version is currently out of date and contains a bug.
 could this be updated to the current version if you are still
 maintaining the code?

I was recently told that the current maintainers address bounces by
someone who is trying to get an update for this port reviewed.  I'm
working with that person to get it into the PR system and eventually
into the tree.

If the maintainer address bounces for me this time I'll make sure to
find an appropriate maintainer for the port.

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


Re: Where should contrib scripts and utilities be installed?

2008-06-10 Thread Peter Pentchev
On Mon, Jun 09, 2008 at 08:54:49PM -0400, Sahil Tandon wrote:
 Jeffrey Goldberg [EMAIL PROTECTED] wrote:
 
  When some project includes a contrib/ directory with its source where 
  should those canonically be installed?
 
  /usr/local/share/$PORT
 
  or
 
 /usr/local/share/doc/$PORT
 
  or someplace else.
 
  In particular, I'm planing on submitting a patch to sysutils/rsnapshot port 
  to also install, somewhere, the contrib directly that comes out of the 
  tarball.
   
 The existence of ports with a -contrib suffix suggests you may need to 
 create a distinct port for the contrib files.  databases/postgresql-contrib, 
 for example.

Actually, that is not strictly necessary.  There are other ports that
do things in slightly different ways:
- some things in contrib/ are merely documentation snippets that
  belong in share/doc/$PACKAGE, as Jeffery suggested
- some things in contrib/ are sample additions, implementations, clients,
  add-ons and such that *might* belong in share/examples/$PACKAGE
- some things in contrib/ are scripts, clients, add-ons and such that
  might also belong in libexec/$PACKAGE (if they are executable files)
  or share/$PACKAGE (if they are not... I can't think of any examples
  right now, but there might be)
- some things in contrib/ are really best left in a separate port :)

For rsnapshot itself - erm, I don't see a contrib/ directory in
its source; do you mean the utils/ directory, or are you looking at
some version that is not in the Ports Collection yet? :)  If it is
utils/ that you mean, then, well, it's actually your choice - the things
there seem to be little scripts that may live in $EXAMPLESDIR, may
live in libexec/rsnapshot/, and may live in a separate rsnapshot-utils
port.  Either way would be fine, at least IMHO.

G'luck,
Peter

-- 
Peter Pentchev  [EMAIL PROTECTED][EMAIL PROTECTED][EMAIL PROTECTED]
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
Hey, out there - is it *you* reading me, or is it someone else?


pgptdjFXaz8cn.pgp
Description: PGP signature


Re: FreeBSD Port: nntpcache-3.0.2_6

2008-06-10 Thread RW
On Tue, 10 Jun 2008 15:43:36 +0200
Reinhard Haller [EMAIL PROTECTED] wrote:

 Hi,
 
 I've problems to get nntpcache working on amd64 architecture. Are
 there known issues or suggestions to get it working.
 
 The original domain (nntpcache.org/com) is no longer allocated, so
 where can I get any informations?


The current site is given in the port pkg-descr file:

http://iq.org/~proff/nntpcache.org/


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


INDEX build optimizations - please review

2008-06-10 Thread Kris Kennaway
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].


The patches remove most of the extraneous command executions required 
for each invocation of bsd.port.mk (e.g. via 'make describe' in a port), 
by replacing external command invocations with shell or make builtins, 
as well as caching of constants.


Another important optimization is to use /rescue/sh instead of /bin/sh 
for index builds.  The former is statically linked and this is much 
faster to execute.


One further change I didn't do would be to move the WWW specification 
from pkg-descr into a Makefile variable (this could be done 
mechanically).  The new 'make describe' target runs entirely using shell 
builtins apart from the need to sed pkg-descr to extract the WWW [2] 
(previously 'describe' was a combination of several shell executions and 
a perl script, invoked for every port).


With these patches an index build on an 8 core system drops from

796.486u 974.564s 5:25.14 544.7%28+193k 37252+719io 27pf+0w

to

642.846u 164.520s 2:31.29 533.6%67+297k 0+721io 0pf+0w

(or with statically linked sed:
637.805u 142.335s 2:27.32 529.5%71+304k 0+720io 0pf+0w
)

The new version requires 69301 forks and 68614 execs (would be ~19000 
fewer of each without WWW in pkg-descr), compared to 252383 forks and 
226875 execs with the current version.


The resulting index is identical except for one port [1] but generating 
it is more than twice as fast (and uses 6 times less system CPU).


I am only getting ~530% CPU utilization because of contention in the 
scheduler, so there is scope for going as low as 100 seconds if this 
went away.  Further improvements are no doubt possible but would require 
profiling the work done within make(1) to see where it is spending its 
time (variable setting, conditional evaluation, loop invocation, regexp 
processing, etc).


**
* NOTE TO PORT DEVELOPERS 
**

Variable assignments with != are bad!  Try as hard as you can to avoid 
using them -- especially in Mk/*!  Every time something processes your 
makefile it will spawn a command, even if it is not relevant for the 
operation being performed.  If you need to run shell commands, try to 
isolate them within a makefile target.  You can avoid code duplication 
by assigning the *shell commands* (not their output) to a variable and 
inserting it into your code block.


e.g. instead of

--
VARIABLE!=  do some shell stuff; do some other stuff

target:
echo ${VARIABLE}
--

do this (or similar):

--
VARIABLE_CMDS=  do some shell stuff; do some other stuff

target:
echo $(${VARIABLE_CMDS})
--

This defers the command execution to the point where the target runs, so 
in the case when the target is *not* run, then you avoid wasting one or 
more process executions.


Kris

[1] This patch exposed a bug: for some reason no dependencies were 
previously recorded for audio/festvox-hvs!  Probably because it only has 
RUN_DEPENDS and the 'make describe' perl script was broken.


[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.



Index: Makefile
===
RCS file: /zoo/cvsup/FreeBSD-CVS/ports/Makefile,v
retrieving revision 1.103
diff -u -r1.103 Makefile
--- Makefile27 Sep 2007 05:36:26 -  1.103
+++ Makefile10 Jun 2008 09:56:17 -
@@ -103,6 +103,7 @@
tmpdir=`/usr/bin/mktemp -d -t index` || exit 1; \
trap rm -rf $${tmpdir}; exit 1 1 2 3 5 10 13 15; \
( cd ${.CURDIR}  make -j${INDEX_JOBS} INDEX_TMPDIR=$${tmpdir} 
BUILDING_INDEX=1 \
+   __MAKE_SHELL=/rescue/sh \
ECHO_MSG=${INDEX_ECHO_MSG} describe ) || \
(rm -rf $${tmpdir} ; \
if [ ${INDEX_QUIET} =  ]; then \
Index: Mk/bsd.java.mk
===
RCS file: /zoo/cvsup/FreeBSD-CVS/ports/Mk/bsd.java.mk,v
retrieving revision 1.82
diff -u -r1.82 bsd.java.mk
--- Mk/bsd.java.mk  28 Oct 2007 15:09:43 -  1.82
+++ Mk/bsd.java.mk  10 Jun 2008 09:56:17 -
@@ -249,34 +249,30 @@
 .  endfor
 
 # Error checking: JAVA_VERSION
+.if !defined(_JAVA_VERSION_LIST_REGEXP)
 _JAVA_VERSION_LIST_REGEXP!=${ECHO_CMD} ${_JAVA_VERSION_LIST} | 
${SED} s/ /\\\|/g
-_ERROR_CHECKING_JAVA_VERSION!= ${ECHO_CMD} ${JAVA_VERSION} | ${TR}   \n \
-   | ${GREP} -v 
${_JAVA_VERSION_LIST_REGEXP} || true
-.

Re: INDEX build optimizations - please review

2008-06-10 Thread Pietro Cerutti

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Kris Kennaway wrote:

| Another important optimization is to use /rescue/sh instead of /bin/sh
| for index builds.  The former is statically linked and this is much
| faster to execute.

True, but the for is not even guaranteed to exist (WITHOUT_RESCUE in
src.conf or similar).

I would opt for checking, and use it only if it exists

| Kris

- --
Pietro Cerutti
[EMAIL PROTECTED]

PGP Public Key:
http://gahr.ch/pgp

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (FreeBSD)

iEYEAREKAAYFAkhOsRUACgkQwMJqmJVx945PpgCeO6ylFV7Lnsizo1p0v9h1jJX1
1RYAn2jwtKuwiy4aXAAsST2CidupEKmO
=hsgo
-END PGP SIGNATURE-
___
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

2008-06-10 Thread Pietro Cerutti

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Pietro Cerutti wrote:
| Kris Kennaway wrote:
|
| | Another important optimization is to use /rescue/sh instead of /bin/sh
| | for index builds.  The former is statically linked and this is much
| | faster to execute.
|
| True, but the for is not even guaranteed to exist (WITHOUT_RESCUE in
| src.conf or similar).

the for??? err... the file I meant..

|
| I would opt for checking, and use it only if it exists
|
| | Kris
|

- --
Pietro Cerutti
[EMAIL PROTECTED]

PGP Public Key:
http://gahr.ch/pgp

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (FreeBSD)

iEYEAREKAAYFAkhOsgMACgkQwMJqmJVx946UagCgoLs7no6NgcLPLSn0lzOHyB0M
4HcAn359kBKeDCevr4IM5cOFfEHh6p6q
=81w7
-END PGP SIGNATURE-
___
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

2008-06-10 Thread Jeremy Messenger

On Tue, 10 Jun 2008 11:45:32 -0500, Kris Kennaway [EMAIL PROTECTED] wrote:

Another important optimization is to use /rescue/sh instead of /bin/sh  
for index builds.  The former is statically linked and this is much  
faster to execute.


I don't have INDEX in all of my systems, so I am only take a peek. What  
about users that have WITHOUT_RESCUE defined or/and something different?  
IMO, I think your patch should have a check on if /rescue/sh exists when  
our src provides optional of WITHOUT_RESCUE and is harmless to kill the  
/rescue.


--
.if exists(/rescue/sh)
__MAKE_SHELL=/rescue/sh
.else
__MAKE_SHELL=/bin/sh
.endif
--

Thanks for hint on 'NOTE TO PORT DEVELOPERS' part as I didn't know about  
VARIABLE!= vs $(${VARIABLE_CMDS}). /me copies it in my note.



--


As for the audio/festvox-hvs issue, probably because of no executables or  
files in RUN_DEPENDS:


--
RUN_DEPENDS=${PORTSDIR}/audio/festival+OGI \
${PORTSDIR}/audio/festlex-poslex \
${PORTSDIR}/audio/festlex-ogi \
${PORTSDIR}/audio/festogi-spanish
--

Cheers,
Mezz


--
[EMAIL PROTECTED]  -  [EMAIL PROTECTED]
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/  -  [EMAIL PROTECTED]
___
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

2008-06-10 Thread Kris Kennaway

Pietro Cerutti wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Pietro Cerutti wrote:
| Kris Kennaway wrote:
|
| | Another important optimization is to use /rescue/sh instead of /bin/sh
| | for index builds.  The former is statically linked and this is much
| | faster to execute.
|
| True, but the for is not even guaranteed to exist (WITHOUT_RESCUE in
| src.conf or similar).

the for??? err... the file I meant..


Yeah, I forgot to add a check for that.

Kris
___
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

2008-06-10 Thread Kris Kennaway

Jeremy Messenger wrote:

On Tue, 10 Jun 2008 11:45:32 -0500, Kris Kennaway [EMAIL PROTECTED] wrote:

Another important optimization is to use /rescue/sh instead of /bin/sh 
for index builds.  The former is statically linked and this is much 
faster to execute.


I don't have INDEX in all of my systems, so I am only take a peek. What 
about users that have WITHOUT_RESCUE defined or/and something different? 
IMO, I think your patch should have a check on if /rescue/sh exists when 
our src provides optional of WITHOUT_RESCUE and is harmless to kill the 
/rescue.


--
.if exists(/rescue/sh)
__MAKE_SHELL=/rescue/sh
.else
__MAKE_SHELL=/bin/sh
.endif
--


Yeah, I will add this in the next version.

Thanks for hint on 'NOTE TO PORT DEVELOPERS' part as I didn't know about 
VARIABLE!= vs $(${VARIABLE_CMDS}). /me copies it in my note.


What would be good is if someone can add it to the porter's handbook.

As for the audio/festvox-hvs issue, probably because of no executables 
or files in RUN_DEPENDS:


--
RUN_DEPENDS=${PORTSDIR}/audio/festival+OGI \
${PORTSDIR}/audio/festlex-poslex \
${PORTSDIR}/audio/festlex-ogi \
${PORTSDIR}/audio/festogi-spanish
--


Ah yes, good catch.  This looks like a port bug, so I don't think I need 
to modify my patches.


Kris

___
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

2008-06-10 Thread Kris Kennaway

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?


Kris
___
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

2008-06-10 Thread 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

2008-06-10 Thread Kris Kennaway

Alex Kozlov wrote:

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


Thanks, I have emailed Max.  What I think I will do is add an .if 
${OSVERSION}  6xx check around it, and keep the old perl script as 
a fallback.  In a couple of years when 6.3 is no longer supported we can 
GC the old code.


Kris
___
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

2008-06-10 Thread Doug Barton

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://.

hth,

Doug

--

This .signature sanitized for your protection

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


how to determine the date a port is installed

2008-06-10 Thread Novembre
Hi all,

Two questions:
1) Is it possible to determine the date a port/package is installed?
2) How can I delete all the ports/packages installed after a certain date?

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


Re: how to determine the date a port is installed

2008-06-10 Thread Jeremy Chadwick
On Wed, Jun 11, 2008 at 12:09:33AM -0500, Novembre wrote:
 Two questions:
 1) Is it possible to determine the date a port/package is installed?

ls -ld /var/db/pkg/port, use the mtime of the directory.

 2) How can I delete all the ports/packages installed after a certain date?

Use a combination of find with the -mtime flag, and pkg_delete.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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


Re: how to determine the date a port is installed

2008-06-10 Thread Garrett Cooper
On Tue, Jun 10, 2008 at 10:09 PM, Novembre [EMAIL PROTECTED] wrote:
 Hi all,

 Two questions:
 1) Is it possible to determine the date a port/package is installed?
 2) How can I delete all the ports/packages installed after a certain date?

 Thanks a lot :)

1. Please don't cross-post.
2. ls -lt /var/db/pkg/*/+DESC piped to whatever language you want to
analyze the dates will provide you the result you want, _unless_
either you modified the file(s)

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