Re: The vim port needs a refresh
On 25 May 2013 15:24, Chris Rees cr...@freebsd.org wrote: On 25 May 2013 11:54, Niclas Zeising zeising+free...@daemonic.se wrote: On 05/25/13 10:50, Chris Rees wrote: Alternatively, perhaps we need an editors/vim-options port Just for the record, editors/vim was (and shells/bash) was converted to optionsNG not too long ago. Ah, that's at least some good news. I notice that it was on yet another maintainer timeout, so that criticism stands. It appears that David is no longer interested. As I see it is not regular maintainer timeout as we hoped. May be really David should be removed from maintainer list. -- Eir Nym ___ 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: [HEADSUP] Staging, packaging and more
Hi, I have question do we really need to build *doc packages every time or we can download prebuilded documentation for stable ports? There's two versions of documentation distributed separately for most ports: doc-source and doc-builded. And there's very few situations when we really need build documentation from scratch. Otherwise we can download prepackaged versions from distribution site. For example, I don't need TeX or docbook distribution on my server to read the documentation I can download directly if I don't really want to build it. On Thursday, October 3, 2013, Andriy Gapon wrote: on 03/10/2013 11:48 Baptiste Daroussin said the following: This also allows lots of new features to come: - Allow to create sub-packages - Allow to create debuginfo packages. I'd like to mention a few other possibilities along the same lines: - doc packages - examples packages - devel packages (headers, tools and other files required for compiling dependent software, but not generally needed for an end user) All open up to a debate, of course. Thank you very much for doing this major step! - Allow to do a lot of sanity check in the staging area to improve our QA -- Andriy Gapon ___ freebsd-ports@freebsd.org javascript:; mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.orgjavascript:; -- -- Eir Nym ___ 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
archivers/unzip vs tar -xf
Since FreeBSD 5.4.0-Release libarchive(3) support to unpack zip files. Why not to use it to unpack distributives to workdir? I've downloaded all distros and tried to unpack them all with tar(1) with no problems. I use FreeBSD 9.0-CURRENT r222717. -- Yours, Eir Nym ___ 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: Best way to uninstall X
On 7 April 2011 21:29, Konstantin Tokarev annu...@yandex.ru wrote: 07.04.2011, 20:59, Attos attos.ja...@gmail.com: Hello all, What is the best way to uninstall X and all the applications that run under X? Thanks in advance. rm -rf /* newfs(8) will be much faster! -- Regards, Konstantin ___ 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 ___ 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
x11-toolkits/gtk30?!
Can somebody tell me what is this port means?! Is this placeholder or joke? directory is same as gtk20 (as diff shows) -- Cheese ___ 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: Mk/bsd.command.mk: missing CSH tag
On 22 November 2010 17:17, Lars Engels lars.eng...@0x20.net wrote: On Fri, Nov 19, 2010 at 08:21:31PM +0300, Eir Nym wrote: On 19 November 2010 18:32, Christian Weisgerber na...@mips.inka.de wrote: Eir Nym eir...@gmail.com wrote: Since when? If you are missing /bin/csh, your system is defective or at least nonstandard. It is good joke, thanks I guess he's talking about the ports tree being too fragile for some non-default configurations and not many people are willing to fix it. I understand this. Port can check this (because it is optional system component) and use another or generate error. This is very confusing. One of us is out of sync with reality. (If it's me, I'd like to know.) Your confident claim that csh is optional is like stating that the sky is green and the sun is purple. Did I miss something? If you think that any part of base system is mandatory, you should write request to remove knob WITHOUT_TCSH and any other, which you think is not optional. If you want support from the FreeBSD community, every part of the base system is mandatory. But you have to check every optional. ___ 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: [Bug 2] USE_PYTHON not used in /etc/make.conf to properly alias installed Python executable
On 19 November 2010 22:14, bugzi...@gthcfoundation.org wrote: http://saya.gthc.org/bugzilla/show_bug.cgi?id=2 e...@gthcfoundation.org changed: What |Removed |Added QAContact| |freebsd-ports@freebsd.org --- Comment #2 from e...@gthcfoundation.org --- test: Added freebsd-ports@freebsd.org for QA contact of this bug! -- Configure bugmail: http://saya.gthc.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA Contact for the bug. ___ 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 You should use PYTHON_VERSION in make.conf(5) to build python ports for your python version as described in bsd.python.mk ___ 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: Mk/bsd.command.mk: missing CSH tag
On 19 November 2010 16:44, Christian Weisgerber na...@mips.inka.de wrote: Eir Nym eir...@gmail.com wrote: Your patch should check if tcsh is in system. it is optional component. Since when? If you are missing /bin/csh, your system is defective or at least nonstandard. It is good joke, thanks -- Christian naddy Weisgerber na...@mips.inka.de ___ 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 ___ 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: Mk/bsd.command.mk: missing CSH tag
On 19 November 2010 17:26, Anonymous swel...@gmail.com wrote: Eir Nym eir...@gmail.com writes: On 19 November 2010 16:44, Christian Weisgerber na...@mips.inka.de wrote: Eir Nym eir...@gmail.com wrote: Your patch should check if tcsh is in system. it is optional component. Since when? If you are missing /bin/csh, your system is defective or at least nonstandard. It is good joke, thanks I guess he's talking about the ports tree being too fragile for some non-default configurations and not many people are willing to fix it. I understand this. Port can check this (because it is optional system component) and use another or generate error. IOW, you can emphasize tcsh(1) being optional by stepping up to maintain shells/tcsh. ;) I prefer to create Makefile for make(1) or gmake(1) for this port or rewrite script to use sh(1) ___ 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: Mk/bsd.command.mk: missing CSH tag
On 19 November 2010 18:32, Christian Weisgerber na...@mips.inka.de wrote: Eir Nym eir...@gmail.com wrote: Since when? If you are missing /bin/csh, your system is defective or at least nonstandard. It is good joke, thanks I guess he's talking about the ports tree being too fragile for some non-default configurations and not many people are willing to fix it. I understand this. Port can check this (because it is optional system component) and use another or generate error. This is very confusing. One of us is out of sync with reality. (If it's me, I'd like to know.) Your confident claim that csh is optional is like stating that the sky is green and the sun is purple. Did I miss something? Yes, I know there is a WITHOUT_TCSH knob. You can use this when you build a FreeBSD-based embedded system where you know you won't need csh. In no way does the existence of this knob imply that csh is optional on a standard FreeBSD system where you build ports. Ok, another example is NIS. You can turn off NIS support in your system, and ports will check NIS biraries if they need them. -- Christian naddy Weisgerber na...@mips.inka.de ___ 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 ___ 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: Mk/bsd.command.mk: missing CSH tag
On 19 November 2010 18:32, Christian Weisgerber na...@mips.inka.de wrote: Eir Nym eir...@gmail.com wrote: Since when? If you are missing /bin/csh, your system is defective or at least nonstandard. It is good joke, thanks I guess he's talking about the ports tree being too fragile for some non-default configurations and not many people are willing to fix it. I understand this. Port can check this (because it is optional system component) and use another or generate error. This is very confusing. One of us is out of sync with reality. (If it's me, I'd like to know.) Your confident claim that csh is optional is like stating that the sky is green and the sun is purple. Did I miss something? If you think that any part of base system is mandatory, you should write request to remove knob WITHOUT_TCSH and any other, which you think is not optional. Yes, I know there is a WITHOUT_TCSH knob. You can use this when you build a FreeBSD-based embedded system where you know you won't need csh. In no way does the existence of this knob imply that csh is optional on a standard FreeBSD system where you build ports. -- Christian naddy Weisgerber na...@mips.inka.de ___ 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 ___ 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: Mk/bsd.command.mk: missing CSH tag
On 19 November 2010 20:47, Anonymous swel...@gmail.com wrote:
Eir Nym eir...@gmail.com writes:
On 19 November 2010 18:32, Christian Weisgerber na...@mips.inka.de wrote:
Eir Nym eir...@gmail.com wrote:
Since when? If you are missing /bin/csh, your system is defective
Yes, I know there is a WITHOUT_TCSH knob. You can use this when
you build a FreeBSD-based embedded system where you know you won't
need csh. In no way does the existence of this knob imply that csh
is optional on a standard FreeBSD system where you build ports.
What are those requirements that constitute standard FreeBSD system
capable of building ports?
Ok, another example is NIS. You can turn off NIS support in your
system, and ports will check NIS biraries if they need them.
There are more examples
- openssl: WITH_OPENSSL_PORT
- pkg_install: .if exists(...)
- fetch: .if exists(...)
- texinfo: by relying on PATH
And rather than resurrecting shells/tcsh one can also also try
BUILD_DEPENDS += ${CSH}:${PORTSDIR}/shells/44bsd-csh
.if exists(/bin/csh)
CSH ?= /bin/csh
.else
CSH ?= ${LOCALBASE}/bin/44bsd-csh
.endif
But some ports may assume csh is tcsh like sh is bash on linux.
Oh, sorry, I haven't knew if csh is in ports tree. thanks
___
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: Mk/bsd.command.mk: missing CSH tag
2010/11/18 O. Hartmann ohart...@zedat.fu-berlin.de:
Hello out there,
I was trying porting some unusual scientific software to the ports
collection (the first time I do) and run into problems. The port does not
have any kind of Makefile environment, it is build and installed via a csh
script. These scripts also seem to run via ${SH}, but it would be nice to
${CSH}. Is it possible to import this tag into
Mk/bsd.command.mk?
I can recommend to create some Makefile (it is very simple) or rewrite
it (it is also very simple)
For example, I have no (t)csh in my system and there no tcsh in ports system..
If you need, I can help you with.
Thanks,
Oliver
___
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
___
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: Mk/bsd.command.mk: missing CSH tag
On 18 November 2010 19:08, Jason Helfman jhelf...@e-e.com wrote:
On Thu, Nov 18, 2010 at 05:21:47PM +0300, Eir Nym thus spake:
2010/11/18 O. Hartmann ohart...@zedat.fu-berlin.de:
Hello out there,
I was trying porting some unusual scientific software to the ports
collection (the first time I do) and run into problems. The port does not
have any kind of Makefile environment, it is build and installed via a
csh
script. These scripts also seem to run via ${SH}, but it would be nice to
${CSH}. Is it possible to import this tag into
Mk/bsd.command.mk?
I can recommend to create some Makefile (it is very simple) or rewrite
it (it is also very simple)
For example, I have no (t)csh in my system and there no tcsh in ports
system..
If you need, I can help you with.
Wrote a quick patch:
--- bsd.commands.mk.orig 2010-11-18 08:05:47.0 -0800
+++ bsd.commands.mk 2010-11-18 08:06:17.0 -0800
@@ -76,6 +76,7 @@
SED?= /usr/bin/sed
SETENV?= /usr/bin/env
SH?= /bin/sh
+CSH?= /bin/csh
SORT?= /usr/bin/sort
STRIP_CMD?= /usr/bin/strip
# Command to run commands as privileged user
Your patch should check if tcsh is in system. it is optional component.
Thanks,
Oliver
___
--
Jason Helfman
System Administrator
experts-exchange.com
http://www.experts-exchange.com/M_4830110.html
___
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: Mk/bsd.command.mk: missing CSH tag
On 18 November 2010 20:18, Rob Farmer rfar...@predatorlabs.net wrote: On Thu, Nov 18, 2010 at 08:13, Eir Nym eir...@gmail.com wrote: On 18 November 2010 19:08, Jason Helfman jhelf...@e-e.com wrote: Wrote a quick patch: --- bsd.commands.mk.orig 2010-11-18 08:05:47.0 -0800 +++ bsd.commands.mk 2010-11-18 08:06:17.0 -0800 @@ -76,6 +76,7 @@ SED?= /usr/bin/sed SETENV?= /usr/bin/env SH?= /bin/sh +CSH?= /bin/csh SORT?= /usr/bin/sort STRIP_CMD?= /usr/bin/strip # Command to run commands as privileged user The patch should probably retain alphabetical order. Your patch should check if tcsh is in system. it is optional component. Why? What do you suggest happens if it isn't found? Nothing will break except stuff that uses the variable and it would use the variable because it needs csh. It is part of the base system (/bin/csh and /bin/tcsh) for all supported releases. Firstly, it is optional part. and I can rewrite build script to make(1) or at least shell script -- Rob Farmer ___ 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: misc/152296: wrong message when trying to checkout using old repository path
On 18 November 2010 20:15, arun...@freebsd.org wrote:
Synopsis: wrong message when trying to checkout using old repository path
State-Changed-From-To: open-suspended
State-Changed-By: arundel
State-Changed-When: Thu Nov 18 16:58:58 UTC 2010
State-Changed-Why:
I'm very sorry for handling this PR inappropriatly. Somehow I was under the
impression that we had a version of svn in the base tree. However that is not
the case!
I think marking this as suspended is the best option for now, since there
was no patch attached to correct svn's handling of the wrong URL.
Since the svn port seems to get updated very regularly we can assume that the
development version of svn is still containing this issue. If somebody wants
to
provide a patch we could try convincing the svn developers to push it upstream
in order to have it in one of the next svn releases and thus ports.
A different approach would be to add a local ports patch to
devel/subversion{-freebsd}/files.
Responsible-Changed-From-To: freebsd-bugs-freebsd-ports
Responsible-Changed-By: arundel
Responsible-Changed-When: Thu Nov 18 16:58:58 UTC 2010
Responsible-Changed-Why:
This is a ports related PR.
http://www.freebsd.org/cgi/query-pr.cgi?pr=152296
___
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
I see only two possible ways to fix this problem:
If you have checkouted source tree before, you can use following
command to relocate it:
find /usr/src -name .svn|xargs -n 1 -J XXX sed -i '.bak'
's,http://svn.freebsd.org/viewvc/base/head/usr.bin/,http://svn.freebsd.org/base/head/usr.bin/,'
XXX/entries
If you can't checkout source tree with wrong url - fix your script,
which check out source tree, but never svn.
___
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: Mk/bsd.command.mk: missing CSH tag
On 18 November 2010 21:00, Rob Farmer rfar...@predatorlabs.net wrote:
On Thu, Nov 18, 2010 at 09:25, Eir Nym eir...@gmail.com wrote:
Firstly, it is optional part.
You didn't answer my question:
.if exists(/bin/csh)
CSH?= /bin/csh
.else
CSH?= # What goes here?
.endif
nope, only CSH?= /bin/csh without any other checks.
Port should check if ${CSH} is exits in the system.
And there no replacement in ports tree for this.
And this variable can be in Makefile for port because it is uncommon.
And I'm aware it can be dropped using a knob. But I don't think port
maintainers should be expected to support anything other than a full
base system. This port needs csh, so it will fail if you don't have
csh.
and I can rewrite build script to
make(1) or at least shell script
Ok, great. But you are still basically saying that certain base system
utilities should be off limits because you have chosen to remove them
from your system.
If you want, you can remove tcsh(1) from your system using
WITHOUT_TCSH in src.conf(5) with rebuilding system, and then removing
obsolete files.
--
Rob Farmer
___
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: misc/152296: wrong message when trying to checkout using old repository path
The following reply was made to PR misc/152296; it has been noted by GNATS.
From: Eir Nym eir...@gmail.com
To: arun...@freebsd.org
Cc: ken...@gmail.com, freebsd-b...@freebsd.org, freebsd-ports@freebsd.org,
FreeBSD Mail Lists bug-follo...@freebsd.org
Subject: Re: misc/152296: wrong message when trying to checkout using old
repository path
Date: Thu, 18 Nov 2010 20:38:48 +0300
On 18 November 2010 20:15, arun...@freebsd.org wrote:
Synopsis: wrong message when trying to checkout using old repository path
State-Changed-From-To: open-suspended
State-Changed-By: arundel
State-Changed-When: Thu Nov 18 16:58:58 UTC 2010
State-Changed-Why:
I'm very sorry for handling this PR inappropriatly. Somehow I was under the
impression that we had a version of svn in the base tree. However that is not
the case!
I think marking this as suspended is the best option for now, since there
was no patch attached to correct svn's handling of the wrong URL.
Since the svn port seems to get updated very regularly we can assume that the
development version of svn is still containing this issue. If somebody wants
to
provide a patch we could try convincing the svn developers to push it
upstream
in order to have it in one of the next svn releases and thus ports.
A different approach would be to add a local ports patch to
devel/subversion{-freebsd}/files.
Responsible-Changed-From-To: freebsd-bugs-freebsd-ports
Responsible-Changed-By: arundel
Responsible-Changed-When: Thu Nov 18 16:58:58 UTC 2010
Responsible-Changed-Why:
This is a ports related PR.
http://www.freebsd.org/cgi/query-pr.cgi?pr=152296
___
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
I see only two possible ways to fix this problem:
If you have checkouted source tree before, you can use following
command to relocate it:
find /usr/src -name .svn|xargs -n 1 -J XXX sed -i '.bak'
's,http://svn.freebsd.org/viewvc/base/head/usr.bin/,http://svn.freebsd.org/base/head/usr.bin/,'
XXX/entries
If you can't checkout source tree with wrong url - fix your script,
which check out source tree, but never svn.
___
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
Old ports bugs analyzis
I work on creating system for system and ports autobuilder with custom
settings for my FreeBSD machines. I know about many programs, which do
same, but I don't like strange depends, which are not controlled by
OPTIONS and some another
I've analyse ports tree and want to say about.
There're lot problems with ports to create per-port PRs
manually.Common types of problems are listed here:
0) Main part of problems in tons of ports, which has hidden options
(WITH WITHOUT checking), but not using OPTIONS for them.
1) There many libraries added with BUILDRUN dependencies, not as LIB-DEPENDS.
2) Some ports has only BUILD depends to libraries, but links them dynamicly.
3) All(?) samba33 slaves define dependency as samba33, and make
warning me about master target redefinition when do something on them.
4) many ports define dependencies as
${.CURDIR}/../../category/dep-port-name
5) And some adds trailing slash.
I want fix these problems, but I have no much time to fix several
thousands of ports. This work (include PR sending) needs about is 1-2
month per 8-10 hours a day.
I put my analysys in several work files:
I've removed ${PORTSDIR} from paths for readability in index files.
http://freebsd.eroese.org/bsd.local.mk - different describe target
(clean and simple)
http://freebsd.eroese.org/portInfo.py - py-IDX maker. old, but enough version.
http://freebsd.eroese.org/tag - portsnap(8) tag
http://freebsd.eroese.org/IDX - special maked IDX
http://freebsd.eroese.org/py-IDX - human readable format of IDX, see
py program for comments about types.
___
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
