port name confliction and lib dir problems about porting
Hi! I'm porting evan's debugger to freebsd, which name will be devel/edb. It's an excellent ollydbg-like debugging tool. Now almost all work has been done, but I run into two problems. 1. There's already one port named edb (databases/edb, Enlightenment Database Library). Is there any convention that I should follow to rename the new port? It has a man file edb.1. What should I do with it after I rename the port, eg, how to rename a file in Makefile? 2. It installs some library files to lib or lib64 based on OS arch. How to specify lib path in pkg-plist? -- B.R. HU Dong ___ 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: [CFT] TexLive port
On 12/08/2012 10:12, Dominic Fandrey wrote: On 31/07/2012 00:48, Dominic Fandrey wrote: I have a well working TexLive 2012 port, intended to be a replacement for teTex. ... Because a lot of things depend on a working TeX install I'd like to have some volunteers in a week. Here we go: http://www.home.hs-karlsruhe.de/~fado1011/texlive/ I'm about ready now. I just need to complete the CONFLICTS. Clearly just anything with teTeX in the name isn't enough. I think I need help figuring this out. Or at least a recommendation. Should I go ahead with a PR and just add ports as people report problems? -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: [CFT] TexLive port
On Mon, Aug 20, 2012 at 09:51:02AM +0200, Dominic Fandrey wrote: On 12/08/2012 10:12, Dominic Fandrey wrote: On 31/07/2012 00:48, Dominic Fandrey wrote: I have a well working TexLive 2012 port, intended to be a replacement for teTex. ... Because a lot of things depend on a working TeX install I'd like to have some volunteers in a week. Here we go: http://www.home.hs-karlsruhe.de/~fado1011/texlive/ I'm about ready now. I just need to complete the CONFLICTS. Clearly just anything with teTeX in the name isn't enough. I think I need help figuring this out. Or at least a recommendation. Should I go ahead with a PR and just add ports as people report problems? Sorry, I must have missed this part in my previous email. The CONFLICTS you have should cover everything. I'm just speculating that the transition would have been smoother if the teTeX ports were deleted in one go before replacing them with portmaster. -- Denny Lin ___ 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: [CFT] TexLive port
On 20/08/2012 10:16, Denny Lin wrote:
On Mon, Aug 20, 2012 at 09:51:02AM +0200, Dominic Fandrey wrote:
On 12/08/2012 10:12, Dominic Fandrey wrote:
On 31/07/2012 00:48, Dominic Fandrey wrote:
I have a well working TexLive 2012 port, intended to be a replacement
for teTex.
...
Because a lot of things depend on a working TeX install I'd like to
have some volunteers in a week.
Here we go:
http://www.home.hs-karlsruhe.de/~fado1011/texlive/
I'm about ready now. I just need to complete the CONFLICTS. Clearly
just anything with teTeX in the name isn't enough. I think I need
help figuring this out.
Or at least a recommendation. Should I go ahead with a PR and just
add ports as people report problems?
Sorry, I must have missed this part in my previous email. The CONFLICTS
you have should cover everything. I'm just speculating that the
transition would have been smoother if the teTeX ports were deleted in
one go before replacing them with portmaster.
I have run into problems with portmaster. The problem is that it doesn't
check whether a dependency is satisfied. It just goes ahead and installs
them.
I think a dependency like:
latex:${PORTSDIR}/print/teTeX-base
shouldn't cause portmaster to install teTeX-base. Not if a latex
binary is already available.
--
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
___
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: [CFT] TexLive port
On 08/20/2012 01:23, Dominic Fandrey wrote:
I have run into problems with portmaster. The problem is that it doesn't
check whether a dependency is satisfied. It just goes ahead and installs
them.
I think a dependency like:
latex:${PORTSDIR}/print/teTeX-base
shouldn't cause portmaster to install teTeX-base. Not if a latex
binary is already available.
Portmaster doesn't handle dependencies that way, it relies on the port
authors to register CONFLICTS. If you have installed a port that
installs a latex binary it and teTeX-base should have CONFLICTS
registered against each other.
Doug
--
I am only one, but I am one. I cannot do everything, but I can do
something. And I will not let what I cannot do interfere with what
I can do.
-- Edward Everett Hale, (1822 - 1909)
___
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: thunderbird-enigmail-1.4.3 build failing on i386 9.1
On 08/13/2012 03:42, Chris Rees wrote: On 13 Aug 2012 12:11, Alex Dupre a...@freebsd.org mailto:a...@freebsd.org wrote: Doug Barton ha scritto: This problem is caused for portmaster by the wacky way that they changed the dependency for thunderbird sources to avoid (zomg!) potential for fetching files related to thunderbird during the enigmail build process. I objected at the time, but my objection was ignored. If you can feel better, I never approved it. It does, actually. :) OTOH, the recent enigmail update worked for me using portmaster, I haven't had time to investigate why it worked this time either. :) Because I put that horrible FETCH_DEPENDS inside a conditional :-) This had a general solution ages ago... but it's still in the queue. http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/169850 This seems perfectly reasonable, and seems also to address the concern about fetching files for a dependent port during the build phase of another. miwi, you requested that PR, where do you stand with it? Doug -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) ___ 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: [CFT] TexLive port
On 20/08/2012 10:40, Doug Barton wrote:
On 08/20/2012 01:23, Dominic Fandrey wrote:
I have run into problems with portmaster. The problem is that it doesn't
check whether a dependency is satisfied. It just goes ahead and installs
them.
I think a dependency like:
latex:${PORTSDIR}/print/teTeX-base
shouldn't cause portmaster to install teTeX-base. Not if a latex
binary is already available.
Portmaster doesn't handle dependencies that way, it relies on the port
authors to register CONFLICTS. If you have installed a port that
installs a latex binary it and teTeX-base should have CONFLICTS
registered against each other.
So evidently my list of CONFLICTS is not complete.
--
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
___
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: thunderbird-enigmail-1.4.3 build failing on i386 9.1
On 08/20/2012 01:45, Doug Barton wrote: On 08/13/2012 03:42, Chris Rees wrote: On 13 Aug 2012 12:11, Alex Dupre a...@freebsd.org mailto:a...@freebsd.org wrote: Doug Barton ha scritto: This problem is caused for portmaster by the wacky way that they changed the dependency for thunderbird sources to avoid (zomg!) potential for fetching files related to thunderbird during the enigmail build process. I objected at the time, but my objection was ignored. If you can feel better, I never approved it. It does, actually. :) OTOH, the recent enigmail update worked for me using portmaster, I haven't had time to investigate why it worked this time either. :) Because I put that horrible FETCH_DEPENDS inside a conditional :-) This had a general solution ages ago... but it's still in the queue. http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/169850 This seems perfectly reasonable, and seems also to address the concern about fetching files for a dependent port during the build phase of another. miwi, you requested that PR, where do you stand with it? Sorry, put the wrong e-mail address in for miwi. -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) ___ 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 name confliction and lib dir problems about porting
On Mon, Aug 20, 2012 at 3:14 PM, HU Dong itechb...@gmail.com wrote: Hi! I'm porting evan's debugger to freebsd, which name will be devel/edb. It's an excellent ollydbg-like debugging tool. Now almost all work has been done, but I run into two problems. 1. There's already one port named edb (databases/edb, Enlightenment Database Library). Is there any convention that I should follow to rename the new port? It has a man file edb.1. What should I do with it after I rename the port, eg, how to rename a file in Makefile? 2. It installs some library files to lib or lib64 based on OS arch. How to specify lib path in pkg-plist? -- B.R. HU Dong Problems solved. Sorry for disturbance. -- B.R. HU Dong ___ 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_version bump? (was: Re: vlc 2.0.3 ProjectM path fix)
On Sat, Aug 18, 2012 at 10:45:10PM +0200, Juergen Lock wrote:
On Wed, Aug 15, 2012 at 10:09:59AM -0700, Kevin Oberman wrote:
On Wed, Aug 15, 2012 at 5:01 AM, Juergen Lock n...@jelal.kn-bremen.de
wrote:
On Tue, Aug 14, 2012 at 09:54:54PM +0200, Olli Hauer wrote:
...
I think I got it: It is only a problem of configuring in the running
vlc. You have to set the right path under
'Settings','All','Audio','Visualizing','projectM'. That's all ;-)
Aah-haah! :) I've fixed the default paths and made a new patch:
http://people.freebsd.org/~nox/tmp/vlc-2.0.3-010.patch
From your patch:
workaround is to deinstall the old vlc-1.x version before building
the new one.
What about a conflict line ?
CONFLICTS_BUILD=${PORTNAME}-1.*
This allows users to fetch the source but they have to deinstall the
old version before building the new one.
Hm well the rtld bug this workaround is for only affects the
pulseaudio and notify knobs, and the workaround doesn't work for
the notify knob so it would only cover half the cases, and also
checking if this is needed in the port would require a
__FreeBSD_version bump which is probably overkill for this bug.
And why is it overkill? I regularly see comments about not wanting to
bump __FreeBSD_version, but it's just an integer (though presented as
a fixed-point fraction). There is no shortage and I never have
understood why people are so hesitant to change it when there is a
real, even if fairly small benefit from the bump.
Hmm. Alexander, what do you think?
Not being Alexander, but appeared on Cc:.
IMO, bumping __FreeBSD_version should not be done frivolous, and routine
bug fixes are definitely not the good reason to bump.
For one, users of HEAD or stable are assumed to run tip of the branch.
If you want defined point of the branch, use release. With this POV,
the usefulness of the bump for bug fix is only a week or two.
Second, bump of __FreeBSD_version signifies major incompatibility between
pre-bumped tree and current one. In the kernel, each bump of version in HEAD
means that new modules cannot be loaded into new kernel.
Bumping for bug fixes is a misuse of the mechanism which was put there
to provide information about major changes in system. For small or
detectable items, use autoconf-like runtime (or build-time *) tests.
* - Usually, the tests must be run-time, and not build-time. This bug is
greatly amplified by use of __FreeBSD_version. The case that initiated
the discussion is probably the first time I ever saw the when build-time
test makes some sense.
pgpoRahquxJaz.pgp
Description: PGP signature
Current unassigned ports problem reports
(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .)
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.
S Tracker Resp. Description
o ports/170781[PATCH] sysutils/cciss_vol_status: take maintainership
f ports/170780[maintainer update] graphichs/zathura-djvu 0.1.1 - 0.
o ports/170779New port: devel/edbg An ollydbg-like debugger based on
o ports/170777[PATCH] Not LIBS but LDFLAGS in Makefile of lang/ruby
f ports/170773sysutils/bacula-server overlaps with sysutils/backula-
o ports/170769pkg_add -v -r pbi-manager
o ports/170768New port: lang/spidermonkey-185 A standalone JavaScrip
o ports/170767[patch] update ports-mgmt/portbuilder from 0.1.5.2 to
o ports/170735Update multimedia/mplayer and mencoder to a recent sna
o ports/170730multimedia/mplayer-skins plist generation under pkgng
f ports/170723[patch] x11-wm/dwm: add optional Xft support
o ports/170704[NEW PORT] games/patapizza-tetris: An unofficial clone
o ports/170695sysutils/fusefs-ntfs - instant reboot when mv from UFS
o ports/170682[NEW PORT] graphics/puckman: An unofficial clone of th
o ports/170674devel/libsysinfo fails to link correctly (missing kvm
o ports/170666New port: graphics/nomacs simple image viewer
o ports/170662[NEW PORT] devel/pymunk: A easy-to-use pythonic 2d phy
o ports/170661[NEW PORT] graphics/py27-pyglet-devel: Cross-platform
o ports/170652New port: net-mgmt/nagios-check_ipmi_sensor: Nagios/Ic
f ports/170641x11-toolkits/open-motif: need mkcatdefs utility
f ports/170626x11-toolkits/open-motif: X11/extensions/XPrint.h is no
o ports/170616gpk-update-viewer
f ports/170610[update]: textproc/ctpp2 up to new version
f ports/170542sysutils/bsdadminscripts does not build correctly in m
f ports/170538x11-wm/enlightenment build breaks
f ports/170537devel/libftdi seems broken on i386 and amd64
f ports/170524devel/ding-libs fails to build in tinderbox
f ports/170502security/sssd failed to connect Ldap server without SA
o ports/170492[REPOCOPY] devel/gwenhywfar - devel/gwenhywfar-{fox16
f ports/170473[patch] audio/alsa-plugins: disable ARIFF_OSS by defau
o ports/170467Unintended effect of /usr/local/include/base64.h in bu
f ports/170457[patch] audio/alsa-lib: implicit declaration of calloc
o ports/170448[NEW PORT] devel/allegro5: Allegro 5 is a game program
f ports/170417Update port: sysutils/grub2 to 2.00
f ports/170381x11/slim window manager gives dbus errors starting xfc
f ports/170366lang/libobjc2: update to 1.6.1
f ports/170365Patch updating finance/trytond from version 1.4.7 to 2
f ports/170357net-mgmt/tcptrack Segmentation fault (core dumped)
f ports/170344[UPDATE] net/tcpflow: update to 1.2.8, take maintainer
f ports/170339www/node: segmentation violation in v8::internal::Hand
o ports/170336New port: textproc/confetti Configuration file parser
o ports/170285Update mail/mailman from 2.1.14 to 2.1.15
o ports/170280mail/mailman reports incorrect value for MM_USERID
o ports/170242[PATCH] devel/arduino: fix avr-libc SIG_USART1_RECV is
o ports/170241[PATCH] devel/libftdi: upgrade to 0.20 and fix automak
o ports/170229sysutils/ntfsprogs is in conflict with sysutils/fusefs
f ports/170186Update sysutils/modules to version 3.2.9
o ports/170185sysutils/mgeupsd not correctly works.
o ports/170180[patch] Mk/bsd.options.mk allow make.conf and command
o ports/170104error setting source interface in net/mcast-tools, net
o ports/170100astro/orsa: version 0.7.0 in ports hopelessly outdated
f ports/170089chinese/ibus-chewing 1.3.10 can't be compiled with ibu
o ports/170016net/liveMedia: update to 2012.07.18 release
o ports/17emulators/vmware-tools6: Can not install VMware Tools
f ports/169876devel/flyspray: Strict Standards: Non-static method Fl
o ports/169861new port: audio/bristol, Bristol Synthesiser Emulation
o ports/169799update multimedia/handbrake to 0.9.6
f ports/169770[patch] audio/alsa-lib: make async handler work (from
f ports/169767audio/alsa-plugins: desync with oss plugin
f ports/169759net-mgmt/nrpe2 doesn't start after subsequent
Current problem reports assigned to po...@freebsd.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). 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. S Tracker Resp. Description p ports/170569 ports sysutils/sec does not start automatically at boot time 1 problem total. ___ 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: devel/zookeeper rc.d script
On Aug 6, 2012, at 03:04 , Doug Barton do...@freebsd.org wrote: On 07/09/2012 08:57, George Neville-Neil wrote: On Jul 9, 2012, at 00:15 , Doug Barton wrote: On 07/08/2012 20:01, George Neville-Neil wrote: On Jul 8, 2012, at 22:39 , Doug Barton wrote: On 07/08/2012 19:33, George Neville-Neil wrote: A followup. zookeeper is now ported to Freebsd (/usr/ports/devel/zookeeper) George, did you see the PR and the followup from me regarding the port? I got a mail from jgh@ but only today figured out what the PR was. Are you not getting your g...@freebsd.org mail? I'll look at the patches from him tomorrow. I copied the text from my message below for your convenience. http://www.freebsd.org/cgi/query-pr.cgi?pr=169693 Furthermore the rc.d script is a mess, and should not have been committed like it was (numerous missing bits, bad format, set_rcvar, hard-coded /usr/local, no REQUIRE, no KEYWORD: shutdown, etc.). Please read http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html and then ask in freebsd-rc@ if you have any additional questions. Sorry to be so blunt, but I'm really, really tired of repeating the same stuff over and over again, and this script is really a mess. Also, don't install the script in do-install, see the web page above (and/or the PR) for USE_RC_SUBR. And FYI, there is no need to have the function in that script. You could use (for example) start_cmd=$command start just as well. Not to mention that the function you have should be using $1 as the argument to $command, not $rc_arg. Reasons why left as an exercise for the reader ... George, Some of these issues were covered by the PR, but many of them were not. If you have any questions about the changes that are needed you should feel free to ask on freebsd...@freebsd.org. I think many or most of these are addressed by updates being made by Steven Kreuzer to both this port and the zookeeper-devel port. Best, George ___ 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: Question about new options framework (regression?)
On Fri, Jul 27, 2012 at 07:02:16PM +0200, Oliver Fromme wrote: Jase Thew wrote: On 27/07/2012 10:41, Baptiste Daroussin wrote: I think that is the more reasonnable, I'll add this when fully back. I was thinking of LATE_SET and LATE_UNSET but OVERRIDE_SET and OVERRIDE_UNSET sounds better to me. What use-case are you thinking of that requires the ability for saved config to override manually specified config? If there isn't a compelling reason for this, then I'd personally much rather see the original behaviour restored rather than adding another two variables. Baptiste is right ... The original behaviour is flawed, because it depends on how the port's maintainer wrote the Makefile. For example, If you have WITH_FOO=YES in the options file, and the port's Makefile checks whether WITH_FOO is set or unset, then there is *no* way to override that, not even with the old options framework. In the case of zsh I was lucky, because the (old) Makefile checked if WITH_ZSH_STATIC is set, while the options file contained WITHOUT_ZSH_STATIC, so I could override that. If it was checking whether WITHOUT_ZSH_STATIC was unset, it wouldn't have worked. Also, if I wanted to do it the other way round, i.e. set WITH_ZSH_STATIC in the options file, there would be no way to unset that on the command line. So, Baptiste's approach to fix that alltogether is right, in my opinion. Best regards Oliver Does this patch fits your needs? http://people.freebsd.org/~bapt/OVERRIDE_BLA.diff The initial configuration has been saved using make config. # make showconfig === The following configuration options are available for zsh-5.0.0: DEBUG=off: Install debug symbols DOCS=off: Build and install the documentation GDBM=on: Enable GDBM support (GPL) MAILDIR=on: Enable support for Maildirs in MAIL(PATH) MEM=off: Enable zsh-mem options MULTIBYTE=on: multibyte character support PCRE=off: Use Perl Compatible Regular Expressions SECURE_FREE=on: Enable zsh-secure-free STATIC=off: Build static executable/libraries === Use 'make config' to modify these settings # OVERRIDE_SET=DOCS make showconfig === The following configuration options are available for zsh-5.0.0: DEBUG=off: Install debug symbols DOCS=on: Build and install the documentation GDBM=on: Enable GDBM support (GPL) MAILDIR=on: Enable support for Maildirs in MAIL(PATH) MEM=off: Enable zsh-mem options MULTIBYTE=on: multibyte character support PCRE=off: Use Perl Compatible Regular Expressions SECURE_FREE=on: Enable zsh-secure-free STATIC=off: Build static executable/libraries === Use 'make config' to modify these settings # OVERRIDE_SET=DOCS OVERRIDE_UNSET=GDBM make showconfig === The following configuration options are available for zsh-5.0.0: DEBUG=off: Install debug symbols DOCS=on: Build and install the documentation GDBM=off: Enable GDBM support (GPL) MAILDIR=on: Enable support for Maildirs in MAIL(PATH) MEM=off: Enable zsh-mem options MULTIBYTE=on: multibyte character support PCRE=off: Use Perl Compatible Regular Expressions SECURE_FREE=on: Enable zsh-secure-free STATIC=off: Build static executable/libraries === Use 'make config' to modify these settings # Sorry for having been long on this. regards, Bapt pgpBYYFID7sJL.pgp Description: PGP signature
Re: __FreeBSD_version bump? (was: Re: vlc 2.0.3 ProjectM path fix)
On Mon, 20 Aug 2012 13:15:10 +0300
Konstantin Belousov kostik...@gmail.com wrote:
On Sat, Aug 18, 2012 at 10:45:10PM +0200, Juergen Lock wrote:
On Wed, Aug 15, 2012 at 10:09:59AM -0700, Kevin Oberman wrote:
On Wed, Aug 15, 2012 at 5:01 AM, Juergen Lock
n...@jelal.kn-bremen.de wrote:
On Tue, Aug 14, 2012 at 09:54:54PM +0200, Olli Hauer wrote:
...
I think I got it: It is only a problem of configuring in
the running vlc. You have to set the right path under
'Settings','All','Audio','Visualizing','projectM'. That's
all ;-)
Aah-haah! :) I've fixed the default paths and made a new
patch:
http://people.freebsd.org/~nox/tmp/vlc-2.0.3-010.patch
From your patch:
workaround is to deinstall the old vlc-1.x version before
building the new one.
What about a conflict line ?
CONFLICTS_BUILD=${PORTNAME}-1.*
This allows users to fetch the source but they have to
deinstall the old version before building the new one.
Hm well the rtld bug this workaround is for only affects the
pulseaudio and notify knobs, and the workaround doesn't work for
the notify knob so it would only cover half the cases, and also
checking if this is needed in the port would require a
__FreeBSD_version bump which is probably overkill for this bug.
And why is it overkill? I regularly see comments about not
wanting to bump __FreeBSD_version, but it's just an integer
(though presented as a fixed-point fraction). There is no
shortage and I never have understood why people are so hesitant
to change it when there is a real, even if fairly small benefit
from the bump.
Hmm. Alexander, what do you think?
Not being Alexander, but appeared on Cc:.
IMO, bumping __FreeBSD_version should not be done frivolous, and
routine bug fixes are definitely not the good reason to bump.
For one, users of HEAD or stable are assumed to run tip of the branch.
If you want defined point of the branch, use release. With this POV,
the usefulness of the bump for bug fix is only a week or two.
Second, bump of __FreeBSD_version signifies major incompatibility
between pre-bumped tree and current one. In the kernel, each bump of
version in HEAD means that new modules cannot be loaded into new
kernel.
Bumping for bug fixes is a misuse of the mechanism which was put there
to provide information about major changes in system. For small or
detectable items, use autoconf-like runtime (or build-time *) tests.
* - Usually, the tests must be run-time, and not build-time. This bug
is greatly amplified by use of __FreeBSD_version. The case that
initiated the discussion is probably the first time I ever saw the
when build-time test makes some sense.
I agree with Konstantin and I do not see the point to bump the version
just to serve fleeting needs of -stable or -current branch users -
their problems will be gone with upgrade to the tip of the respective
branch and this is the first thing they are expected to do before
reporting a bug anyway.
--
Alexander Kabaev
signature.asc
Description: PGP signature
pkg(ng)/portupgrade-devel: does not respect setting of USE_GCC= 4.6+
I utilize FreeBSD 10.0-CURRENT and build the OS with CLANG as well as
ports, which are compatible building with clang, using the well known
settings in /etc/make.conf and /etc/src/conf.
I use ports-mgmt/pkg (1.0-r6) and recently in combination with
ports-mgmt/portupgrade for maintaining my ports. Prior to portupgrade I
used to use ports-mgmt/portmaster (with patch).
In /etc/mak.conf, I include a file via
.include /usr/local/etc/ports.conf in which I have settings like those:
# math/fftw3
.if ${.CURDIR:M/usr/ports/math/fftw3}
USE_GCC=4.6+
#CC=cc
#CXX= c++
#CPP= cpp
.endif
This setup worked very well in pre-pkg(ng) times and with portmaster.
But now, with pkg, I can not install math/fftw3 anymore (amongst other
ports not compatible with CLANG). Performing make install in
math/fftw3 results in:
=== fftw3-3.3.2 : clang does not support OpenMP. Disable the OPENMP
option or use another compiler.
*** [install] Error code 1
Stop in /usr/ports/math/fftw3.
Using portupgrade ends up in this:
portupgrade -f math/fftw3
USING PKGNG
** Port marked as IGNORE: math/fftw3:
: clang does not support OpenMP. Disable the OPENMP option or
use another compiler
** Listing the failed packages (-:ignored / *:skipped / !:failed)
- math/fftw3 (marked as IGNORE)
I'd like to have OPENMP since I have multicore CPUs running and
therefore I use GCC 4.6 (or higher), which is capable of.
Why does the use of pkg(ng) reject those essential settings? Have I
overlooked something essential? I can not find any remarks on that
subject in the man pages, or any hint leading towards a new configure
schematics. Any hint?
Regards and greetings,
Oliver
P.S. Please CC me in email, I do not subscribe list ports@freebsd.
signature.asc
Description: OpenPGP digital signature
Re: devel/zookeeper rc.d script
On 08/20/2012 08:43, George Neville-Neil wrote: On Aug 6, 2012, at 03:04 , Doug Barton do...@freebsd.org wrote: On 07/09/2012 08:57, George Neville-Neil wrote: On Jul 9, 2012, at 00:15 , Doug Barton wrote: On 07/08/2012 20:01, George Neville-Neil wrote: On Jul 8, 2012, at 22:39 , Doug Barton wrote: On 07/08/2012 19:33, George Neville-Neil wrote: A followup. zookeeper is now ported to Freebsd (/usr/ports/devel/zookeeper) George, did you see the PR and the followup from me regarding the port? I got a mail from jgh@ but only today figured out what the PR was. Are you not getting your g...@freebsd.org mail? I'll look at the patches from him tomorrow. I copied the text from my message below for your convenience. http://www.freebsd.org/cgi/query-pr.cgi?pr=169693 Furthermore the rc.d script is a mess, and should not have been committed like it was (numerous missing bits, bad format, set_rcvar, hard-coded /usr/local, no REQUIRE, no KEYWORD: shutdown, etc.). Please read http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html and then ask in freebsd-rc@ if you have any additional questions. Sorry to be so blunt, but I'm really, really tired of repeating the same stuff over and over again, and this script is really a mess. Also, don't install the script in do-install, see the web page above (and/or the PR) for USE_RC_SUBR. And FYI, there is no need to have the function in that script. You could use (for example) start_cmd=$command start just as well. Not to mention that the function you have should be using $1 as the argument to $command, not $rc_arg. Reasons why left as an exercise for the reader ... George, Some of these issues were covered by the PR, but many of them were not. If you have any questions about the changes that are needed you should feel free to ask on freebsd...@freebsd.org. I think many or most of these are addressed by updates being made by Steven Kreuzer to both this port and the zookeeper-devel port. Thanks! Steven, if you have any questions, feel free to shoot them over to freebsd-rc@. -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) ___ 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: pkg(ng)/portupgrade-devel: does not respect setting of USE_GCC= 4.6+
On 8/20/2012 12:57 PM, O. Hartmann wrote:
I utilize FreeBSD 10.0-CURRENT and build the OS with CLANG as well as
ports, which are compatible building with clang, using the well known
settings in /etc/make.conf and /etc/src/conf.
I use ports-mgmt/pkg (1.0-r6) and recently in combination with
ports-mgmt/portupgrade for maintaining my ports. Prior to portupgrade I
used to use ports-mgmt/portmaster (with patch).
In /etc/mak.conf, I include a file via
.include /usr/local/etc/ports.conf in which I have settings like those:
# math/fftw3
.if ${.CURDIR:M/usr/ports/math/fftw3}
USE_GCC=4.6+
#CC=cc
#CXX= c++
#CPP= cpp
.endif
This setup worked very well in pre-pkg(ng) times and with portmaster.
But now, with pkg, I can not install math/fftw3 anymore (amongst other
ports not compatible with CLANG). Performing make install in
math/fftw3 results in:
=== fftw3-3.3.2 : clang does not support OpenMP. Disable the OPENMP
option or use another compiler.
*** [install] Error code 1
Stop in /usr/ports/math/fftw3.
Using portupgrade ends up in this:
portupgrade -f math/fftw3
USING PKGNG
** Port marked as IGNORE: math/fftw3:
: clang does not support OpenMP. Disable the OPENMP option or
use another compiler
** Listing the failed packages (-:ignored / *:skipped / !:failed)
- math/fftw3 (marked as IGNORE)
I'd like to have OPENMP since I have multicore CPUs running and
therefore I use GCC 4.6 (or higher), which is capable of.
Why does the use of pkg(ng) reject those essential settings? Have I
overlooked something essential? I can not find any remarks on that
subject in the man pages, or any hint leading towards a new configure
schematics. Any hint?
FWIF, the IGNORE is unrelated to portupgrade or pkgng. You'll get this
same IGNORE line without using them.
Regards and greetings,
Oliver
P.S. Please CC me in email, I do not subscribe list ports@freebsd.
___
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: pkg(ng)/portupgrade-devel: does not respect setting of USE_GCC= 4.6+
On 20/08/2012 18:57, O. Hartmann wrote:
I utilize FreeBSD 10.0-CURRENT and build the OS with CLANG as well as
ports, which are compatible building with clang, using the well known
settings in /etc/make.conf and /etc/src/conf.
I use ports-mgmt/pkg (1.0-r6) and recently in combination with
ports-mgmt/portupgrade for maintaining my ports. Prior to portupgrade I
used to use ports-mgmt/portmaster (with patch).
In /etc/mak.conf, I include a file via
I take it this is a typo in your e-mail and you really meant to say
/etc/make.conf ?
.include /usr/local/etc/ports.conf in which I have settings like those:
# math/fftw3
.if ${.CURDIR:M/usr/ports/math/fftw3}
USE_GCC=4.6+
#CC=cc
#CXX= c++
#CPP= cpp
.endif
This setup worked very well in pre-pkg(ng) times and with portmaster.
But now, with pkg, I can not install math/fftw3 anymore (amongst other
ports not compatible with CLANG). Performing make install in
math/fftw3 results in:
=== fftw3-3.3.2 : clang does not support OpenMP. Disable the OPENMP
option or use another compiler.
*** [install] Error code 1
Stop in /usr/ports/math/fftw3.
Using portupgrade ends up in this:
portupgrade -f math/fftw3
USING PKGNG
** Port marked as IGNORE: math/fftw3:
: clang does not support OpenMP. Disable the OPENMP option or
use another compiler
** Listing the failed packages (-:ignored / *:skipped / !:failed)
- math/fftw3 (marked as IGNORE)
I'd like to have OPENMP since I have multicore CPUs running and
therefore I use GCC 4.6 (or higher), which is capable of.
Why does the use of pkg(ng) reject those essential settings? Have I
overlooked something essential? I can not find any remarks on that
subject in the man pages, or any hint leading towards a new configure
schematics. Any hint?
Regards and greetings,
Oliver
P.S. Please CC me in email, I do not subscribe list ports@freebsd.
Hi, Oliver,
This technique certainly should work: I use some pretty similar
constructs in several machines with various combinations of pkg_tools,
pkgng, portmaster and poudriere, and it's absolutely fine there.
pkgng doesn't do anything to affect the actual extract / patch /
configure / build / install phases -- that's all still exactly the same,
and all of the various ports related make variables should work in the
same way as before. In fact, the only place pkgng gets involved is
during the 'fake-pkg' and 'package' targets which happen right after the
software has been installed. All that does is process the various
package metadata (plist, recording dependencies, checksums etc) and
updates the database in /var/db/pkg/local.sqlite and optionally builds a
tarball out of the installed files.
Hmm... can you check the environment you used while building? Several
variables can have a significant effect. PORTSDIR, PORT_DBDIR -- but
pespecially __MAKE_CONF might be the culprit. Except, as you can see,
__MAKE_CONF has got that __ prefix, which signifies not a user
serviceable part.
Your ports tree is definitely in the usual place of /usr/ports?
Verb. Sap. -- I usually write those tests against .CURDIR like this:
.if ${.CURDIR:M*/net-mgmt/net-snmp}
NET_SNMP_MIB_MODULES=host disman/event-mib mibII/mta_sendmail
mibII/tcpTable ucd-snmp/diskio
.endif
so that they still work even if I'm using a ports tree in a non-standard
place.
Another test would be:
% make -C /usr/ports/math/fftw3 -V USE_GCC
If that doesn't result in 4.6+ then something is broken in make.conf or
ports.conf somewhere.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
Re: pkg(ng)/portupgrade-devel: does not respect setting of USE_GCC= 4.6+
Am 08/20/12 21:07, schrieb Matthew Seaman:
On 20/08/2012 18:57, O. Hartmann wrote:
I utilize FreeBSD 10.0-CURRENT and build the OS with CLANG as well as
ports, which are compatible building with clang, using the well known
settings in /etc/make.conf and /etc/src/conf.
I use ports-mgmt/pkg (1.0-r6) and recently in combination with
ports-mgmt/portupgrade for maintaining my ports. Prior to portupgrade I
used to use ports-mgmt/portmaster (with patch).
In /etc/mak.conf, I include a file via
I take it this is a typo in your e-mail and you really meant to say
/etc/make.conf ?
Correct, it is a type, the file's name is /etc/make.conf.
.include /usr/local/etc/ports.conf in which I have settings like those:
# math/fftw3
.if ${.CURDIR:M/usr/ports/math/fftw3}
USE_GCC=4.6+
#CC=cc
#CXX= c++
#CPP= cpp
.endif
This setup worked very well in pre-pkg(ng) times and with portmaster.
But now, with pkg, I can not install math/fftw3 anymore (amongst other
ports not compatible with CLANG). Performing make install in
math/fftw3 results in:
=== fftw3-3.3.2 : clang does not support OpenMP. Disable the OPENMP
option or use another compiler.
*** [install] Error code 1
Stop in /usr/ports/math/fftw3.
Using portupgrade ends up in this:
portupgrade -f math/fftw3
USING PKGNG
** Port marked as IGNORE: math/fftw3:
: clang does not support OpenMP. Disable the OPENMP option or
use another compiler
** Listing the failed packages (-:ignored / *:skipped / !:failed)
- math/fftw3 (marked as IGNORE)
I'd like to have OPENMP since I have multicore CPUs running and
therefore I use GCC 4.6 (or higher), which is capable of.
Why does the use of pkg(ng) reject those essential settings? Have I
overlooked something essential? I can not find any remarks on that
subject in the man pages, or any hint leading towards a new configure
schematics. Any hint?
Regards and greetings,
Oliver
P.S. Please CC me in email, I do not subscribe list ports@freebsd.
Hi, Oliver,
Hello Matthew,
This technique certainly should work: I use some pretty similar
constructs in several machines with various combinations of pkg_tools,
pkgng, portmaster and poudriere, and it's absolutely fine there.
pkgng doesn't do anything to affect the actual extract / patch /
configure / build / install phases -- that's all still exactly the same,
and all of the various ports related make variables should work in the
same way as before. In fact, the only place pkgng gets involved is
during the 'fake-pkg' and 'package' targets which happen right after the
software has been installed. All that does is process the various
package metadata (plist, recording dependencies, checksums etc) and
updates the database in /var/db/pkg/local.sqlite and optionally builds a
tarball out of the installed files.
Hmm... can you check the environment you used while building? Several
variables can have a significant effect. PORTSDIR, PORT_DBDIR -- but
pespecially __MAKE_CONF might be the culprit. Except, as you can see,
__MAKE_CONF has got that __ prefix, which signifies not a user
serviceable part.
Your ports tree is definitely in the usual place of /usr/ports?
Yes, it is definitely located at /usr/ports. /usr/ports is, in all of my
installations, a separate partition, i.e:
/dev/gpt/usr.ports 29G3.8G 23G14%/usr/ports
Verb. Sap. -- I usually write those tests against .CURDIR like this:
.if ${.CURDIR:M*/net-mgmt/net-snmp}
NET_SNMP_MIB_MODULES=host disman/event-mib mibII/mta_sendmail
mibII/tcpTable ucd-snmp/diskio
.endif
so that they still work even if I'm using a ports tree in a non-standard
place.
This is a very good idea, I will adobt this ...
Another test would be:
% make -C /usr/ports/math/fftw3 -V USE_GCC
This results in:
4.6+
If that doesn't result in 4.6+ then something is broken in make.conf or
ports.conf somewhere.
I assume we can exclude this.
I'm pretty sure, that the last time I updated port math/fftw3 I wanted
option OpenMP enabled so I declared USE_GCC=4.6+ in make.conf. Later,
also working!, I excluded all these user definitions into an external
file called ports.conf located in /usr/local/etc (I like this clean
separation of OS and user messes ;-) ). Suddenly it doesn't work
anymore. There were changes in several Mk files located in /usr/ports/Mk.
Strange:
sysutils/cdrtools is also marked to be compiled with USE_GCC=4.6+ and
when I recompile the already installed port via
portupgrade -f cdrtools
I see a lot of those console exposures:
gcc46 -O2 -fno-strict-aliasing -pipe -pipe -O3 -fno-strict-aliasing
-march=native -Wl,-rpath=/usr/local/lib/gcc46 -DSCHILY_BUILD
-IOBJ/amd64-freebsd-cc -I../incs/amd64-freebsd-cc -I../include
-I/usr/local/include -I/usr/local/include -I../libscg -I../cdrecord
-DSCHILY_PRINT -c -o OBJ/amd64-freebsd-cc/dmaresid.o dmaresid.c
pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule
Hi all, Since 1.0-rc6 release, everything looks ready for a final release of 1.0, I'll give more details on the release commit bit :) this is planned for 30th august 2012. Current was supposed to switch to pkgng by default today, it has been delayed until the nvidia-driver is fixed with pkgng. Thanksfully kwm@ and danfe@ has been working on this, and the situation should be fixed pretty soon. Please continue testing pkgng and reporting bugs, if you are new comers do not hesitate to ask question about pkgng so that we can improve documentation: The usual links about pkgng: - http://wiki.freebsd.org/pkgng - http://wiki.freebsd.org/PkgPrimer - https://github.com/pkgng/pkgng/blob/master/FAQ.md - http://people.freebsd.org/~bapt/pres-pkgng-bsdcan.pdf - http://www.youtube.com/watch?v=4Hxq7AHZ27I regards, Bapt pgpO2nsFSuifW.pgp Description: PGP signature
Re: pkg(ng)/portupgrade-devel: does not respect setting of USE_GCC= 4.6+
On 2012-08-20 19:57, O. Hartmann wrote:
I utilize FreeBSD 10.0-CURRENT and build the OS with CLANG as well as
ports, which are compatible building with clang, using the well known
settings in /etc/make.conf and /etc/src/conf.
I use ports-mgmt/pkg (1.0-r6) and recently in combination with
ports-mgmt/portupgrade for maintaining my ports. Prior to portupgrade I
used to use ports-mgmt/portmaster (with patch).
In /etc/mak.conf, I include a file via
.include /usr/local/etc/ports.conf in which I have settings like those:
# math/fftw3
.if ${.CURDIR:M/usr/ports/math/fftw3}
USE_GCC=4.6+
#CC=cc
#CXX= c++
#CPP= cpp
.endif
[...]
Maybe you can find the issue with the command
$ script -q TMPOUT_v make -d v
or
$ script -q TMPOUT_A make -d A
do not scare, really much output.
Regards,
olli
___
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: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule
Baptiste Daroussin b...@freebsd.org wrote: Please [...] ask question about pkgng [...] What would be the best practice of mixing ports with packages? The use case I have in mind is compiling Xorg ports locally WITH_NEW_XORG and WITH_KMS, and using packages from pkgbeta.freebsd.org for everything else. Is there some mixture of pkg and portmaster flags that allows this kind of setup? ___ 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: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule
On Tue, Aug 21, 2012 at 12:09:46AM +0300, Vitaly Magerya wrote: Baptiste Daroussin b...@freebsd.org wrote: Please [...] ask question about pkgng [...] What would be the best practice of mixing ports with packages? The use case I have in mind is compiling Xorg ports locally WITH_NEW_XORG and WITH_KMS, and using packages from pkgbeta.freebsd.org for everything else. Is there some mixture of pkg and portmaster flags that allows this kind of setup? ___ 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 There is no best practice for that unfortunatly, (as actually) the best for you is maybe to build your own pkgng repostories? http://wiki.freebsd.org/PkgPrimer#Using_poudriere for example? We are open to suggestion here :) regards, Bapt pgpx14W5LyN3x.pgp Description: PGP signature
