FW: [Richard Stallman] Emacs 22.1 released
Hi all, As you can see in the following quote, Richard Stallman has announced the much anticipated Emacs 22 release. % Date: Sun, 03 Jun 2007 20:17:24 -0400 % From: Richard Stallman [EMAIL PROTECTED] % To: [EMAIL PROTECTED] % Subject: Emacs 22.1 released % Message-ID: [EMAIL PROTECTED] % % GNU Emacs 22.1 has been released. It is available on the GNU ftp % sites at ftp.gnu.org/gnu/emacs/ and its mirrors (see % http://www.gnu.org/order/ftp.html). % % The MD5 check-sum is the following: % % 6949df37caec2d7a2e0eee3f1b422726 emacs-22.1.tar.gz % % Please send any bug reports to [EMAIL PROTECTED] You can use the % function M-x report-emacs-bug to do this. This release has been in the works several years, and we already have a port which builds pre-release snapshots of GNU Emacs 22 in our Ports tree (this is the editors/emacs-devel port). I've been maintaining on and off the editors/emacs-devel port for some time, with the kind help of many people who submitted PRs and/or even wholesale updates to newer pre-release snapshots, but I don't know if I am sufficiently experienced with the Ports tree to maintain _the_ official editors/emacs port. Bearing this in mind, what is the usual way we like handling upgrades of this sort or magnitude for our Emacs-depending ports? Should we keep the editors/emacs-devel port, update it to Emacs 22.1 and allow for some time of 'settling in' before we switch editors/emacs to the 22.1 version? Then when the time comes to switch editors/emacs to editors/emacs21 how should we handle the 'move' (i.e. do we repo-move the files?)? If we do the repo-move, what is the process of making sure all the Ports which depend on editors/emacs21 keep working, and how do we handle ports which use editors/emacs (emacs22 by then)? With these questions in mind, I will be glad and grateful for any insight you can offer, so that we can handle the transition to Emacs 22.1 as smoothly as possible, and with the least amount of problems for our end-users :-) Regards, Giorgos ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FW: [Richard Stallman] Emacs 22.1 released
Giorgos Keramidas escribió: Should we keep the editors/emacs-devel port, update it to Emacs 22.1 and allow for some time of 'settling in' before we switch editors/emacs to the 22.1 version? It depends on the specific situation and the decision of the maintainer(s). If it makes sense to have the next devel snapshot, it is ok to keep both ports. (And if the release cycle is such long for emacs I think it does make sense.) Then when the time comes to switch editors/emacs to editors/emacs21 how should we handle the 'move' (i.e. do we repo-move the files?)? We always repo-*copy* and remove from the old location instead of repo-moves, so that we have the removed files in Attic for later tracking and have a MOVED entry so that users could recognize the change. Or when the port is updated, we just update the old copy (emacs) and keep the duplicate (emacs21) previous version with the new name. If we do the repo-move, what is the process of making sure all the Ports which depend on editors/emacs21 keep working, and how do we handle ports which use editors/emacs (emacs22 by then)? You should just edit the dependencies of the individual ports to use the correct port to depend on. I don't have too much emacs knowledge, thus I don't know how to decide in each case, which one to depend on, but if possible, we usually use the latest stable version as a dependency. If all dependants work with emacs 22, then probably, you won't have to change them to emacs21, just upgrade emacs. With these questions in mind, I will be glad and grateful for any insight you can offer, so that we can handle the transition to Emacs 22.1 as smoothly as possible, and with the least amount of problems for our end-users :-) In this case, I'd ask for a repo-copy from emacs - emacs21, update emacs to 22, and update emacs-devel to 22.1 if there's such, or remove that if that's not necessary. More info about repo-copies: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/ports.html Cheers, -- Gabor Kovesdan FreeBSD Volunteer EMAIL: [EMAIL PROTECTED] .:|:. [EMAIL PROTECTED] WEB: http://people.FreeBSD.org/~gabor .:|:. http://kovesdan.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/share/mk/sys.mk and FORTRAN on -CURRENT
Steve Kargl wrote:
On Sun, Jun 03, 2007 at 04:47:33PM -0700, Don Lewis wrote:
I was taking a look at why math/lapack fails to build on -CURRENT and
discovered that the port uses ${FC} to find the FORTRAN compiler. I
then discovered that /usr/share/mk/sys.mk defines ${FC} as f77 (or
fort77). I don't this is appropriate since f77 has been removed from
-CURRENT.
I don't know what the proper fix is, but I though I should point out the
problem ...
There are two bugs here. 1) FC should be removed. 2) The
various ports that use Fortran should use gfortran42
installed with lang/gcc42.
Not only that. f77 in gcc-4.2 has some bugs that are waiting to be
worked out in 4.2.1, so that may be a part of the issue as well.
-Garrett
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/share/mk/sys.mk and FORTRAN on -CURRENT
Hi,
On 4 Jun 2007, at 02:09, Steve Kargl wrote:
On Sun, Jun 03, 2007 at 04:47:33PM -0700, Don Lewis wrote:
I was taking a look at why math/lapack fails to build on -CURRENT and
discovered that the port uses ${FC} to find the FORTRAN compiler. I
then discovered that /usr/share/mk/sys.mk defines ${FC} as f77 (or
fort77). I don't this is appropriate since f77 has been removed from
-CURRENT.
I don't know what the proper fix is, but I though I should point
out the
problem ...
There are two bugs here. 1) FC should be removed.
Why? One might well want the option to use any of the several FORTRAN
compilers from ports.
2) The various ports that use Fortran should use gfortran42
installed with lang/gcc42.
The various ports that use Fortran should be checked to see what
version of FORTRAN they want. I suspect the easiest fix is to have
$FC empty by default and for dependent ports to output a helpful
diagnostic.
A better fix would be to make ports dependent on an appropriate
compiler port, but that's a lot of work and some users will prefer
ifc anyway.
--
Steve
--
Bob Bishop +44 (0)118 940 1243
[EMAIL PROTECTED] fax +44 (0)118 940 1295
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make update broken
[LoN]Kamikaze ha scritto: Make update is broken on my system. Due to the removal of PORTSNAP_UPDATE it now complains about a missing PORTSSUPFILE (SUP_UPDATE is defined for updating /usr/src) instead of using portsnap. I've already notified portmgr and proposed two solutions for this issue. Hopefully it will be fixed soon. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade -o
on 02/06/2007 10:41 Sergey Matveychuk said the following: Andriy Gapon wrote: [snip] The problem can be illustrated like follows: $ portupgrade -o audio/portaudio2 portaudio-18.1_2 ... nothing happens ... $ portupgrade -f -o audio/portaudio2 portaudio-18.1_2 ... portaudio-18.1_2 from audio/portaudio is re-installed ... Does anybody else see this ? [snip] It's possible if installed version is greater than a version in origin. You can compare two version with the command: pkg_version -t version1 version2 I am not sure which versions I should compare... Version of audio/portaudio in ports is 18.1_2, installed version is also 18.1_2. Version of portaudio2 should not matter in this because it is a totally different port, right ? Anyway, even if I had the version situation that you suggested I think it still would be a bug on portupgrade's side because in this case I am not upgrading any ports at all, I am replacing one port with another. Or am I missing something ? -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Current unassigned ports problem reports
Current FreeBSD problem reports The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. Bugs can be in one of several states: o - open A problem report has been submitted, no sanity checking performed. a - analyzed The problem is understood and a solution is being sought. f - feedback Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution. p - patched A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open. r - repocopy The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion. s - suspended The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended. c - closed A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned. Critical problems S Tracker Resp. Description o ports/112754VERY SERIOUS security bug in sysutils/eject f ports/112756www/plone update to 2.5.3 for security fix of XSS vuln f ports/113259security/ossec-hids-server, multiple critical problems f ports/113260security/ossec-hids-client 4 problems total. Serious problems S Tracker Resp. Description o ports/105549ports/www/squid_radius_auth doesn't work on sparc64 o ports/106369vpnd caused kernel panic with ppp mode o ports/106372vpnd can't run with slip mode o ports/107536editors/scite: Can't write on SciTE text editor f ports/108077www/linux-flashplugin9 crashes linux-firefox f ports/108413net/vnc does not works. f ports/108537print/hplip: Build failure f ports/108606Courier MTA terminates abnormaly after installation f ports/108748mod_fcgid 1.10 does not work inside jail f ports/109160net/samba3 crashes freebsd when accessing a share resi f ports/110035Port fix for sysutils/be_agent f ports/110454Joomla port Makefile has incorrect url for package f ports/110943start-dccifd chowns /var/run to user dcc f ports/111012quagga's ripd does not see ng interfaces f ports/51ports/lang/stklos: l/bin/stklos-install is a buggy she o ports/111224[PATCH] security/pam_per_user conflicts with security/ f ports/111338graphics/yafray: doesn't respect CXX, CXXFLAGS and eve o ports/111462syslog-ng2 default configuration file path o ports/111923[PATCH] databases/unixODBC overwrites config file on p f ports/111966Clamav-milter no up o ports/112067ports/paraview 2.4.4 does not compile properly f ports/112083mail/qsheff overwrites configuration upon upgrade f ports/112094www/lynx: plist missing configuration file o ports/112097print/ghostscript-gpl-nox11 compile fails due to missi f ports/112118[PATCH] sysutils/pipemeter: fix crashes o ports/112197[MAINTAINER UPDATE]: devel/libstrfunc upgrade to 8.3 f ports/112277MD5 and SHA256 mismatch for science/hdf5 f ports/112287www/rt36: add missed patches for MULTIPLE_INSTANCES o ports/112385sysutils/lookupd on Kernel 64 f ports/112468sysutils/bacula-server 2.0.3 port build fails for sqli o ports/112545print/ghostscript-gpl 8.54 fail without all driver (or o ports/112652net/freeradius: exited on signal 10 when used with sql f ports/112698www/opera's spell-check doesn't work o ports/112739audio/midimountain doesn't work as patched o ports/112793editors/e3 problem: one line patch to fix bad syscall f ports/112921x11-wm/Beryl not loading focus and keybinding settings f ports/112988print/HPLIP portupgrade failure f ports/113068net/Samba 3.0.25 broken if force user/force group to l f ports/113139sysutils/ucspi-tcp runtime crash on amd64 w/ fix o ports/113159Unbreak x11-toolkits/gtkada-gcc port after transition f ports/113198net/samba3 3.0.25 build failure f ports/113212www/jesred: Fix incompatibility with Squid 2.6 f ports/113235[patch] dns/maradns problem with startup during boot 43 problems total. Non-critical problems S Tracker Resp.
Re: net-im/psi build fails on CURRENT
On Sun, Jun 03, 2007 at 05:13:11PM -0700, Doug Barton wrote: Marek Holly wrote: Hi, I am trying to build psi but I get following error: There is a 0.11-RC1 available (http://forum.psi-im.org/thread/4447), but it requires Qt4 and QCA2. We seem to have the former, but don't seem to have the latter. Shaun, any interest in working this up? I'll see what I can do. Shaun -- Shaun Amott // PGP: 0x6B387A9A A foolish consistency is the hobgoblin of little minds. - Ralph Waldo Emerson ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FW: [Richard Stallman] Emacs 22.1 released
Gabor Kovesdan [EMAIL PROTECTED] writes: Giorgos Keramidas escribió: Should we keep the editors/emacs-devel port, update it to Emacs 22.1 and allow for some time of 'settling in' before we switch editors/emacs to the 22.1 version? It depends on the specific situation and the decision of the maintainer(s). If it makes sense to have the next devel snapshot, it is ok to keep both ports. (And if the release cycle is such long for emacs I think it does make sense.) I had to read that a few times before I was sure I understood it, but now that I've done so, I think it's obviously correct. ;-) The fact that the emacs and emacs-devel ports have different maintainers may call for a little more coordination than usual, but as keramida@ suggested, there's no reason to make the big moves yet. If we do the repo-move, what is the process of making sure all the Ports which depend on editors/emacs21 keep working, and how do we handle ports which use editors/emacs (emacs22 by then)? You should just edit the dependencies of the individual ports to use the correct port to depend on. I don't have too much emacs knowledge, thus I don't know how to decide in each case, which one to depend on, but if possible, we usually use the latest stable version as a dependency. If all dependants work with emacs 22, then probably, you won't have to change them to emacs21, just upgrade emacs. With these questions in mind, I will be glad and grateful for any insight you can offer, so that we can handle the transition to Emacs 22.1 as smoothly as possible, and with the least amount of problems for our end-users :-) There aren't really many ports that depend directly on emacs, and most of them will work on the new version fine. Of course, testing is trickier than most updates, because you can't depend on building and starting the program as an indication that the dependency has been filled properly (because most of the ports are LISP that only gets exercised when actually executed). leim ports may be more of an issue... ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sed errors through portupgrade
Parv wrote: sed: 1: s|^\(@comment[: unbalanced brackets ([]) sed: 1: s|^\(@comment[: unbalanced brackets ([]) sed: 1: s|^\(@comment[: unbalanced brackets ([]) sed: 1: s|^\(@comment[: unbalanced brackets ([]) The above lines are displayed twice: once when portupgrade starts and once when it finishes. What version of portupgrade is producing the error message? What The latest non-devel version (I'm away from the machine now). command did/do you issue? portupgrade port_name. It doesn't depend on what port I'm updating. I think it might be a corruption in /var/db/pkg but I don't know which port is in error. signature.asc Description: OpenPGP digital signature
Re: /usr/share/mk/sys.mk and FORTRAN on -CURRENT
On Mon, Jun 04, 2007 at 01:48:01AM -0700, Garrett Cooper wrote:
Steve Kargl wrote:
On Sun, Jun 03, 2007 at 04:47:33PM -0700, Don Lewis wrote:
I was taking a look at why math/lapack fails to build on -CURRENT and
discovered that the port uses ${FC} to find the FORTRAN compiler. I
then discovered that /usr/share/mk/sys.mk defines ${FC} as f77 (or
fort77). I don't this is appropriate since f77 has been removed from
-CURRENT.
I don't know what the proper fix is, but I though I should point out the
problem ...
There are two bugs here. 1) FC should be removed. 2) The
various ports that use Fortran should use gfortran42
installed with lang/gcc42.
Not only that. f77 in gcc-4.2 has some bugs that are waiting to be
worked out in 4.2.1, so that may be a part of the issue as well.
There isn't an 'f77' in gcc-4.2. There is gfortran, which is a
Fortran 95 comiler with several Fortran 2003 extension. There
are only a few bugs (ie 2 or 3) in corner cases that affect the
ability to compile code which conforms to the Fortran 77 standard.
--
Steve
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/share/mk/sys.mk and FORTRAN on -CURRENT
On Mon, Jun 04, 2007 at 09:43:03AM +0100, Bob Bishop wrote:
Hi,
On 4 Jun 2007, at 02:09, Steve Kargl wrote:
On Sun, Jun 03, 2007 at 04:47:33PM -0700, Don Lewis wrote:
I was taking a look at why math/lapack fails to build on -CURRENT and
discovered that the port uses ${FC} to find the FORTRAN compiler. I
then discovered that /usr/share/mk/sys.mk defines ${FC} as f77 (or
fort77). I don't this is appropriate since f77 has been removed from
-CURRENT.
I don't know what the proper fix is, but I though I should point
out the
problem ...
There are two bugs here. 1) FC should be removed.
Why? One might well want the option to use any of the several FORTRAN
compilers from ports.
The correct spelling of the name of the language is Fortran.
The reason is simple. If you upgrade from 6-stable to 7-current
and you do not clean out the f77 command (aka g77) then you
may have ABI issues when LAPACK is compiled with f77 and consumers
of liblapack.a use gfortran or even the base system cc.
2) The various ports that use Fortran should use gfortran42
installed with lang/gcc42.
The various ports that use Fortran should be checked to see what
version of FORTRAN they want. I suspect the easiest fix is to have
$FC empty by default and for dependent ports to output a helpful
diagnostic.
A better fix would be to make ports dependent on an appropriate
compiler port, but that's a lot of work and some users will prefer
ifc anyway.
The work has already been done for most ports. Lapack is one of the
few that doesn't use gfortran42 by default. See
http://www.freebsd.org/cgi/getmsg.cgi?fetch=313584+318166+/usr/local/www/db/text/2007/freebsd-ports/20070318.freebsd-ports
--
Steve
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Gnome Terminal artifacts
On Sat, 2 Jun 2007 20:34:50 -0400 Indigo 23 [EMAIL PROTECTED] wrote: I upgraded both vte to vte-0.16.4_1 (after supping my ports) and reinstalled gnome-terminal again (just in case) and the artifact problem still exists. Anyone else still experiencing it after updating vte? (Xfce Terminal) After upgrading vte and rebuilding the terminal, artifacts (and black holes) disappeared. Nikola Lečić ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade -o
Andriy Gapon wrote: on 02/06/2007 10:41 Sergey Matveychuk said the following: Andriy Gapon wrote: [snip] The problem can be illustrated like follows: $ portupgrade -o audio/portaudio2 portaudio-18.1_2 ... nothing happens ... $ portupgrade -f -o audio/portaudio2 portaudio-18.1_2 ... portaudio-18.1_2 from audio/portaudio is re-installed ... Does anybody else see this ? [snip] It's possible if installed version is greater than a version in origin. You can compare two version with the command: pkg_version -t version1 version2 I am not sure which versions I should compare... Version of audio/portaudio in ports is 18.1_2, installed version is also 18.1_2. Version of portaudio2 should not matter in this because it is a totally different port, right ? Anyway, even if I had the version situation that you suggested I think it still would be a bug on portupgrade's side because in this case I am not upgrading any ports at all, I am replacing one port with another. Or am I missing something ? I would say it's a feature of portupgrade. It always checks versions by design. -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/share/mk/sys.mk and FORTRAN on -CURRENT
Hi, On 4 Jun 2007, at 16:14, Steve Kargl wrote: On Mon, Jun 04, 2007 at 09:43:03AM +0100, Bob Bishop wrote: [...]A better fix would be to make ports dependent on an appropriate compiler port, but that's a lot of work and some users will prefer ifc anyway. The work has already been done for most ports. Lapack is one of the few that doesn't use gfortran42 by default. See http://www.freebsd.org/cgi/getmsg.cgi?fetch=313584+318166+/usr/ local/www/db/text/2007/freebsd-ports/20070318.freebsd-ports OK, I wasn't aware of that good work because I don't read -ports. Thanks -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade -o
on 04/06/2007 18:26 Sergey Matveychuk said the following: Andriy Gapon wrote: on 02/06/2007 10:41 Sergey Matveychuk said the following: Andriy Gapon wrote: [snip] The problem can be illustrated like follows: $ portupgrade -o audio/portaudio2 portaudio-18.1_2 ... nothing happens ... $ portupgrade -f -o audio/portaudio2 portaudio-18.1_2 ... portaudio-18.1_2 from audio/portaudio is re-installed ... Does anybody else see this ? [snip] It's possible if installed version is greater than a version in origin. You can compare two version with the command: pkg_version -t version1 version2 I am not sure which versions I should compare... Version of audio/portaudio in ports is 18.1_2, installed version is also 18.1_2. Version of portaudio2 should not matter in this because it is a totally different port, right ? Anyway, even if I had the version situation that you suggested I think it still would be a bug on portupgrade's side because in this case I am not upgrading any ports at all, I am replacing one port with another. Or am I missing something ? I would say it's a feature of portupgrade. It always checks versions by design. Even when switching between things like fam and gamin ? I'd say that it is a wrong design then, because I can not imagine any good reason for such behavior. Anyway, what about the real problem as described in the beginning ? I've recently seen another similar report on the list. P.S. version of audio/portaudio2 seems to be 19.b1175. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
startup scripts executed twice after X11R6 and local merge
Maybe the suggestion to add local_startup=/usr/local/etc/rc.d to /etc/rc.conf after the merge should be added to /usr/ports/UPDATING. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: exim PORT -- when to use? when to 'go manual'?
On Jun 4, 2007, at 10:01 AM, snowcrash+freebsd wrote: i've just installed exim on a small freebsd-based router -- via PORTS install -- as a sendmail replacement. no probs, either. now, I want to upgrade exim on that router to add 'just' DNSBL-filtering on the router, and have it function as a transparent gateway to another lan-based, exim router. Does that upgrade involve a different version of the exim tarball than the one used in ports, or is the change that you need somewhere else? do folks recommend still using the PORT install? It depends. iiuc, general advice for PORTS is use the port, don't touch the port ... true? if so, how/where do I configure exim if not mod'ing the port's MAKEFILE? Make your own patch of the port and keep that some place that won't be over written by portsnap or whatever you use to keep your ports tree up to date. Then have a script that patches your port tree after you do such an update. Of course you should submit your patch to the port to the port maintainer. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: exim PORT -- when to use? when to 'go manual'?
hi, now, I want to upgrade exim on that router to add 'just' DNSBL-filtering on the router, and have it function as a transparent gateway to another lan-based, exim router. Does that upgrade involve a different version of the exim tarball than the one used in ports, bad choice of words on my part :-/ nope. i simply mean, here, same version as ports, just turning on the capability(ies) as i normally do in from-src builds in Local/Makefile. thos config params are, in the port, in ITS 'Makefile' ... hence, config changes would be changing the included port files. iiuc. or is the change that you need somewhere else? just in Makefile -- used for the COMPILE phase -- and local RUNTIME config options like ip-per-domain specification, etc etc do folks recommend still using the PORT install? It depends. heh. yup. Make your own patch of the port and keep that some place that won't be over written by portsnap or whatever you use to keep your ports tree up to date. Then have a script that patches your port tree after you do such an update. hm. now that you mention it, i suppose that the PORT /may/ be setup to look for upgrade-proof config files in (non?)standard locations. i'll dig-about and look ... i admit, as great (!) as PORTS are, i'm just not yet used to NOT 'doing it all' myself. Of course you should submit your patch to the port to the port maintainer. good point. thanks! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: package font-adobe-utopia-type1-1.0.1 has no origin recorded
On Sunday 03 June 2007 19:43:56 martinko wrote: Hallo, I've installed new X.org 7.2 on clean 6.2-STABLE system and everything went fine except for the following package: pkg_version: font-adobe-utopia-type1-1.0.1 does not appear to be a valid package! I tried to reinstall it but that didn't help (see below). also i could not install some port (don't remember which one) due to issue with the above mentioned package. What happens if you try to reinstall it manually (via cd /usr/ports/x11-fonts/font-adobe-utopia-type1 make deinstall make reinstall)? Dejan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
INDEX build failed for 5.x
INDEX build failed with errors:
Generating INDEX-5 - please wait..pkg_info: not found
pkg_info: not found
pkg_info: not found
Makefile, line 108: Malformed conditional (${USE_GNOME:Mgtk12} ||
${USE_GNOME:Mimlib})
Makefile, line 111: if-less else
Makefile, line 113: if-less endif
make: fatal errors encountered -- cannot continue
=== x11/metisse failed
*** Error code 1
*** Error code 1
Stop in /local0/tmp/erwin/tindex/ports.
*** Error code 1
Stop in /local0/tmp/erwin/tindex/ports.
1 error
Committers on the hook:
ahze cy danfe dinoex edwin erwin foxfair gabor lesi miwi osa pav
Most recent CVS update was:
U MOVED
U devel/p5-ExtUtils-CBuilder/Makefile
U devel/p5-ExtUtils-CBuilder/distinfo
U devel/p5-ExtUtils-CBuilder/pkg-plist
U lang/p5-Interpolation/Makefile
U lang/p5-Interpolation/distinfo
U math/p5-Math-BigInt-GMP/Makefile
U math/p5-Math-BigInt-GMP/distinfo
U security/libfwbuilder/Makefile
U security/libfwbuilder/distinfo
U security/libfwbuilder/pkg-plist
U textproc/Makefile
U www/Makefile
U x11/libXpm/Makefile
U x11/libXpm/pkg-plist
U x11/libdmx/Makefile
U x11/libdmx/pkg-descr
U x11/libxkbui/Makefile
U x11/libxkbui/pkg-descr
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
