Re: [CFT] pkg-plist generator
On Mon, 27 Mar 2017 20:33:46 +0800
Ben Woods <woods...@gmail.com> wrote:
> On 26 March 2017 at 01:14, Dominic Fandrey <kamik...@bsdforen.de> wrote:
>
> > Since February I have been working on a pkg-plist generator that
> > understands and handles options. I believe it is now ready for public
> > testing as a part of my bsda2 script collection:
> >
>
> I had a similar idea for adding this functionality to the poudriere
> testport command, which I mentioned here:
> https://github.com/freebsd/poudriere/issues/303
This is actually a big deal, because you have to obey a lot of rules
like OPTIONS_SINGLE, OPTIONS_MULTI ${opt}_IMPLIES, ${opt}_PREVENTS etc.
The script itself is about 1.3 kLOC long, if you count the shared code
it goes up to 3.6 kLOC.
lines words chars
12994827 34535 src/makeplist.sh
12064378 29901 src/bsda_obj.sh
4731517 10010 src/bsda_container.sh
154 6003969 src/pkg_info.sh
31210886984 src/bsda_opts.sh
85 2651442 src/bsda_util.sh
82 3131889 src/bsda_bsdmake.sh
3611 12988 88730 total
It's not huge, but it's not exactly small either.
> I never got around to implementing anything though... it staid just an
> idea. Looking forward to trying yours.
I'm looking forward to your feedback!
--
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?
pgpWZkMIEmz4Z.pgp
Description: PGP signature
[CFT] pkg-plist generator
Since February I have been working on a pkg-plist generator that understands and handles options. I believe it is now ready for public testing as a part of my bsda2 script collection: https://github.com/lonkamikaze/bsda2/releases/tag/0.2.0-rc1 Testing all combinations of options would mean performing 2^n (n being the number of options) build/stage cycles. I.e. it is a feat only applicable to the smallest, most simple ports. My concession to that fact is that I assume that options do not affect which files other options install. The makeplist script runs one build/stage cycle for each option to determine which files are installed by it. You can grab the tar ball, unpack it and run the script right from where you are: % bsda2-0.2.0-rc1/src/makeplist origin/port To read the manual without installing run: % man bsda2-0.2.0-rc1/man/makeplist.8 Skip ahead to the EXAMPLES section. -- 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? pgpxAbN7mBIHE.pgp Description: PGP signature
Re: testing the value of ${CXX} in ports Makefile
On 30/01/2015 07:28, Don Lewis wrote:
On 29 Jan, Elizabeth Myers wrote:
On 01/29/15 21:43, Don Lewis wrote:
I need to test the value of ${CXX} in the Makefile for a port and am
getting unexpected results. Here is a simplified version of the
Makefile:
...
USE_GCC=4.9+
.include bsd.port.pre.mk
post-patch:
echo CXX=${CXX}
.if ${CXX} == g++49
echo detected g++49
.else
echo did not detect g++49
.endif
.include bsd.port.post.mk
...
Why do you need to detect it? Shouldn't USE_GCC ensure it's there? In
any case, browsing through the ports tree, you could try .if
!empty(CXX:M*g++49*)
With USE_GCC=yes, CXX will currently get set to g++48, but at some point
the default version will get upgraded to 4.9. Unfortunately, that
breaks the port build unless I apply an extra patch to the source. I
could set USE_GCC=4.8, but once the default version of gcc gets updated,
anyone who uses the port will need both gcc 4.8 for this port and 4.9
for the majority of parts that just use USE_GCC=yes to get the default.
Just check against: ${GCC_DEFAULT:M4.9}
--
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: Staging issue with staging of net-im/libpurple (libtool?)
On 20/05/2014 22:13, Tijl Coosemans wrote:
On Tue, 20 May 2014 08:52:46 -0700 Kevin Oberman wrote:
Removed the FIND and re-built. After the build I looked in
stage/usr/local/lib and the .so.0 files are still present! I then installed
with no errors. I'll admit that I don't understand what is happening or why
the touch of the files would break things, but it seems to be fixed, now.
The touch didn't always give all files the same timestamp so sometimes
make thought the configure script was out of date and regenerated it
erasing any patches that had been applied to it.
I figure something like:
find FOO -exec touch {} +
would do the trick.
--
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: Staging issue with staging of net-im/libpurple (libtool?)
On 20/05/2014 14:55, Tijl Coosemans wrote:
On Tue, 20 May 2014 14:14:49 +0200 Albert Shih wrote:
Le 20/05/2014 à 14:09:45+0200, Tijl Coosemans a écrit
On Tue, 20 May 2014 10:55:44 +0200 Albert Shih wrote:
Le 18/05/2014 à 21:11:16-0700, Kevin Oberman a écrit
I have a problem installing net-im/libpurple. I get the following error:
=== Registering installation for libpurple-2.10.9_2
pkg-static:
lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libjabber.so.0):
No such file or directory
pkg-static:
lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/liboscar.so.0):
No such file or directory
pkg-static:
lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libymsg.so.0):
No such file or directory
pkg-static:
lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple-client.so.0):
No such file or directory
pkg-static:
lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple.so.0):
No such file or directory
*** Error code 74
Stop.
Wherethis gets really weird is that on another system it installed
correctly. I wanted to look at the stage directory content, so deinstalled
and reinstalled. Now it won't install there, either. Same error. Why did
it
only install once?
Exact same problem for me. I got two PC, one laptop, another desktop, both
with FreeBSD 10-stable, both using portupgrade.
On one everything work (the desktop), on the laptop I have exact same
message.
The last command in the port Makefile is this:
@${FIND} ${WRKSRC} -type f | ${XARGS} ${TOUCH}
Try removing that line.
Change nothing.
Still get the same error
=== Checking if net-im/libpurple already installed
=== Registering installation for libpurple-2.10.9_2
pkg-static:
lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libjabber.so.0):
No such file or directory
pkg-static:
lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/liboscar.so.0):
No such file or directory
pkg-static:
lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libymsg.so.0):
No such file or directory
pkg-static:
lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple-client.so.0):
No such file or directory
pkg-static:
lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple.so.0):
No such file or directory
*** Error code 74
with
[root@io libpurple]# tail Makefile
${WRKSRC}/libpurple/purple-send-async
@${REINPLACE_CMD} -e 's|/python|/env python|' \
${WRKSRC}/libpurple/purple-remote \
${WRKSRC}/libpurple/purple-url-handler
.if defined(PIDGIN_SLAVE)
@${FIND} ${BUILD_WRKSRC} -name Makefile.in | ${XARGS}
${REINPLACE_CMD} -e \
's|$$(top_builddir)/libpurple/libpurple.la|-lpurple|'
.endif
.include bsd.port.post.mk
[root@io libpurple]#
Silly question perhaps, but did you run make clean before rebuilding?
I turned MYSPACE support of and reproduced the problem. Then I tried
with MYSPACE and it works. Afterwards I tried again without MYSPACE
and it still works.
Then I turned MYSPACE back on and got the error again.
Looks like a timing issue to me. I'd say turn MAKE_JOBS off.
--
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: ACTION REQUIRED - Unstaged Ports being DEPRECATED on June 31st.
On 10/05/2014 17:33, Bryan Drewery wrote: You are receiving this mail as it affects FreeBSD ports that you maintain. In September 2013, the Ports framework learned how to Stage ports. On June 31st, all unstaged ports will be marked DEPRECATED and have their MAINTAINER reset. On August 31st, all unstaged ports will be removed from the ports tree. That's hardly fair with maintainer-updates not being committed for months. I usually stop updating my ports when that happens and resume my activity when my confidence that stuff has a chance of being committed is restored. I.e. when all my old updates have been committed. -- 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: New port, what's next?
On 10/04/2014 20:28, Baptiste Daroussin wrote: On Thu, Apr 10, 2014 at 07:32:31PM +0200, Dominic Fandrey wrote: On 10/04/2014 18:53, Helmut Schneider wrote: I created a new port, Typo3-LTS. The tgz contains - Makefile - distinfo - pkg-plist - pkg-descr - a diff from www/typo3 The file has ~150kB so I assume it's to big for a PR. I assume the bulk of that is the pkg-plist. The largest pkg-plist in the ports tree is 4M. In my opinion huge plists should be dynamically generated, but in your case I'd just I'd just temp-host the file somewhere and file a PR with a link and a checksum. Regards ... autoplist is dangerous because we have no way to control that what is package is what the maintainer expect to be packaged! therefore we often end up with unoticed problems The majority of problems I used to have as a port maintainer stemmed from fiddling with plists. I.e. my experience is the opposite, manual plists lead to errors. Autogenerated plists (which I use in most cases, because dynamic ones are against policy) have reduced the amount of mistakes I make tremendously. -- 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: New port, what's next?
On 10/04/2014 23:14, Lars Engels wrote: On Thu, Apr 10, 2014 at 08:37:45PM +0200, John Marino wrote: On 4/10/2014 20:28, Baptiste Daroussin wrote: On Thu, Apr 10, 2014 at 07:32:31PM +0200, Dominic Fandrey wrote: On 10/04/2014 18:53, Helmut Schneider wrote: I created a new port, Typo3-LTS. The tgz contains - Makefile - distinfo - pkg-plist - pkg-descr - a diff from www/typo3 The file has ~150kB so I assume it's to big for a PR. I assume the bulk of that is the pkg-plist. The largest pkg-plist in the ports tree is 4M. In my opinion huge plists should be dynamically generated, but in your case I'd just I'd just temp-host the file somewhere and file a PR with a link and a checksum. Autoplist are harmful! and should be avoided as much as possible, I know python and ruby has it but I m really not happy about that autoplist is dangerous because we have no way to control that what is package is what the maintainer expect to be packaged! therefore we often end up with unoticed problems Yes, but 6,000 - 20,000 line plists are unwieldy to say the least. And the danger can be mitigated by the maintainer by reviewing the internal temporary package list, ideally on multiple platforms. Also some plists are really hard to make manually if there are many options or if the plist morphs depending on the combination of options. yes, a safety net is removed with a generated plist but it has it's place. The maintainer just has to be vigilant. Can't we teach the ports system to handle pkg-plist.gz? That would be easy enough. The question is, can svn handle it? -- 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: New port, what's next?
On 10/04/2014 18:53, Helmut Schneider wrote: I created a new port, Typo3-LTS. The tgz contains - Makefile - distinfo - pkg-plist - pkg-descr - a diff from www/typo3 The file has ~150kB so I assume it's to big for a PR. I assume the bulk of that is the pkg-plist. The largest pkg-plist in the ports tree is 4M. In my opinion huge plists should be dynamically generated, but in your case I'd just I'd just temp-host the file somewhere and file a PR with a link and a checksum. Regards -- 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: Installing port texlive-base-20120701_10 needs staging disabled
On 06/04/2014 23:31, Dr. Peter Voigt wrote: I have just tried to upgrade to texlive-base-20120701_10 on 10.0-RELEASE. Building of print/texlive-base worked fine but installation failed. As a shot in the dark I tried with portmaster -m -DNO_STAGE -D -G print/texlive-base I ran into this too. It either means the port does not support staging properly, or the plist is broken. In which case you just created an inconsistency. One that luckily heals with the next upgrade. -- 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: DESTDIR support broken?
On 19/11/2013 18:44, Dominic Fandrey wrote: On 18/11/2013 20:28, Kimmo Paasiala wrote: On Mon, Nov 18, 2013 at 10:05 AM, Dominic Fandrey kamik...@bsdforen.de wrote: On 18/11/2013 04:10, Eitan Adler wrote: On Thu, Nov 14, 2013 at 1:00 PM, Dominic Fandrey kamik...@bsdforen.de wrote: # make DESTDIR=/root/tmpdest install === Creating some important subdirectories Are you sure you don't mean make PREFIX=/root/tmpdest/ ? Yes. -- I would expect DESTDIR=/some/path just work for any port. Last commit to bsd.destdir was over a year ago so either it has been broken for a long time or some other more recent commit has broken it. /root/tmpdest is a complete FreeBSD chroot (I did a make installworld distribution DESTDIR=/root/tmpdest right beforehand). I tried several ports, they all exhibit the same failure. The issue is that BSD make (in stable/10) passes set -e to the shell by default. I submitted the details and a fix: http://www.freebsd.org/cgi/query-pr.cgi?pr=184170 -- 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: DESTDIR support broken?
On 22/11/2013 14:17, Peter Pentchev wrote: On Fri, Nov 22, 2013 at 02:02:28PM +0100, Dominic Fandrey wrote: On 19/11/2013 18:44, Dominic Fandrey wrote: On 18/11/2013 20:28, Kimmo Paasiala wrote: On Mon, Nov 18, 2013 at 10:05 AM, Dominic Fandrey kamik...@bsdforen.de wrote: On 18/11/2013 04:10, Eitan Adler wrote: On Thu, Nov 14, 2013 at 1:00 PM, Dominic Fandrey kamik...@bsdforen.de wrote: # make DESTDIR=/root/tmpdest install === Creating some important subdirectories Are you sure you don't mean make PREFIX=/root/tmpdest/ ? Yes. -- I would expect DESTDIR=/some/path just work for any port. Last commit to bsd.destdir was over a year ago so either it has been broken for a long time or some other more recent commit has broken it. /root/tmpdest is a complete FreeBSD chroot (I did a make installworld distribution DESTDIR=/root/tmpdest right beforehand). I tried several ports, they all exhibit the same failure. The issue is that BSD make (in stable/10) passes set -e to the shell by default. I submitted the details and a fix: http://www.freebsd.org/cgi/query-pr.cgi?pr=184170 Hmm, even if this is so, I wonder if there would not be another funny problem later: for ports that actually use staging, ... I tested the fix with a port that I just converted to staging. No problems there. The staging happens on the host system, but the resulting package is correctly installed into DESTDIR. -- 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: DESTDIR support broken?
On 22/11/2013 14:17, Peter Pentchev wrote: On Fri, Nov 22, 2013 at 02:02:28PM +0100, Dominic Fandrey wrote: On 19/11/2013 18:44, Dominic Fandrey wrote: On 18/11/2013 20:28, Kimmo Paasiala wrote: On Mon, Nov 18, 2013 at 10:05 AM, Dominic Fandrey kamik...@bsdforen.de wrote: On 18/11/2013 04:10, Eitan Adler wrote: On Thu, Nov 14, 2013 at 1:00 PM, Dominic Fandrey kamik...@bsdforen.de wrote: # make DESTDIR=/root/tmpdest install === Creating some important subdirectories Are you sure you don't mean make PREFIX=/root/tmpdest/ ? Yes. -- I would expect DESTDIR=/some/path just work for any port. Last commit to bsd.destdir was over a year ago so either it has been broken for a long time or some other more recent commit has broken it. /root/tmpdest is a complete FreeBSD chroot (I did a make installworld distribution DESTDIR=/root/tmpdest right beforehand). I tried several ports, they all exhibit the same failure. The issue is that BSD make (in stable/10) passes set -e to the shell by default. I submitted the details and a fix: http://www.freebsd.org/cgi/query-pr.cgi?pr=184170 Hmm, even if this is so, I wonder if there would not be another funny problem later: for ports that actually use staging, bsd.stage.mk tries to pass a DESTDIR of its own to upstream's build system, so the DESTDIR specified on the make(1) command line might not be passed to upstream's build system at all. So bsd.destdir.mk might do its thing, but then bsd.stage.mk would override the DESTDIR setting during the actual build and installation of the upstream sources, so I wonder if anything at all would be installed into the chroot. bsd.stage.mk sets DESTDIR in MAKE_ARGS, which does not affect the ports infrastructure at all. Instead it is passed to the make run in the WRKSRC by the default do-build and do-install targets. Where it is commonly picked up by build/install systems such as auto-tools generated stuff to install into chroots. This results in the port being installed into STAGEDIR where the ports system the creates a package. And pkg install installs it into the actual DESTDIR. It is not affected by MAKE_ARGS. -- 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: DESTDIR support broken?
On 18/11/2013 20:28, Kimmo Paasiala wrote: On Mon, Nov 18, 2013 at 10:05 AM, Dominic Fandrey kamik...@bsdforen.de wrote: On 18/11/2013 04:10, Eitan Adler wrote: On Thu, Nov 14, 2013 at 1:00 PM, Dominic Fandrey kamik...@bsdforen.de wrote: # make DESTDIR=/root/tmpdest install === Creating some important subdirectories Are you sure you don't mean make PREFIX=/root/tmpdest/ ? Yes. -- I would expect DESTDIR=/some/path just work for any port. Last commit to bsd.destdir was over a year ago so either it has been broken for a long time or some other more recent commit has broken it. /root/tmpdest is a complete FreeBSD chroot (I did a make installworld distribution DESTDIR=/root/tmpdest right beforehand). I tried several ports, they all exhibit the same failure. -- 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: DESTDIR support broken?
On 18/11/2013 04:10, Eitan Adler wrote: On Thu, Nov 14, 2013 at 1:00 PM, Dominic Fandrey kamik...@bsdforen.de wrote: # make DESTDIR=/root/tmpdest install === Creating some important subdirectories Are you sure you don't mean make PREFIX=/root/tmpdest/ ? Yes. -- 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
DESTDIR support broken?
# make DESTDIR=/root/tmpdest install === Creating some important subdirectories realpath: /root/tmpdest/___temp___: No such file or directory *** Error code 1 Stop. make: stopped in /usr/ports/ports-mgmt/pkg That used to be a nice feature for populating chroots/jails. -- 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: Is it or isn't it installed? (It is, but ports tries to again, doomed to fail.)
On 05/11/2013 14:55, Chad J. Milios wrote: TLDR; check lines prefixed with ? in the transcript below. Ran into this over a couple weeks ago. Checked again with last night's portsnap, same problem, same ports. Figured I ought to pipe up about it. Seems like a good ol' classic mystery. I don't know if it's just one instance of a general problem in the way dependencies get detected and dispatched to be installed, maybe just in the python infrastructure, a bug in the net/py-kombu port (which my eyes couldn't find a problem with), or what. I looked into it for an hour before punting with a trivial workaround and moving on, didn't think much of it at the time, figuring it was just one of those temporary problems smarter minds are already hard at work fixing. Apparently they weren't or didn't. This time I'm using a squeaky clean new amd64 9.2-RELEASE-p1 system (empty /usr/local then installing all ports from the same snapshot of /usr/ports). ***How to reproduce: Just happen to already have the dependency devel/py-boto (py27-boto-2.14.0) or devel/py-pyzmq (py27-pyzmq-2.2.0) installed (and their port dirs since cleaned up) when you try to install net/py-kombu (py27-kombu-3.0.1) from ports with BOTO and/or ZMQ options. (In my case I have all its options on.) ... === Checking if devel/py-boto already installed ?=== py27-boto-2.14.0 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of devel/py-boto without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** [check-already-installed] Error code 1 Stop in /usr/ports/devel/py-boto. *** [run-depends] Error code 1 Stop in /usr/ports/net/py-kombu. root@shikamaru:/usr/ports/net/py-kombu # ... Stop in /usr/ports/net/py-kombu. root@shikamaru:/usr/ports/net/py-kombu # That looks like the dependencies in net/py-kombu are broken. I.e. they refer to files that are not/no longer installed by the dependencies. -- 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: bsdadminscripts and pkng
On 01/11/2013 00:58, Jakub Lach wrote: any plans for updating those? Kind of. I just don't know when. -- 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: State of the Porters' Handbook
On 29/10/2013 22:02, Gabor Pali wrote: On Mon, Oct 28, 2013 at 4:11 PM, Baptiste Daroussin b...@freebsd.org wrote: I do buy this argument :) and I'll see want I can do for that in the next couple of days. Please find a patch [1] (and see [2] for the HTML preview) for the porters-handbook document to address this problem. Note that some of the contents have been already updated by Eitan Adler, this is just a continuation of the work. [1] http://people.freebsd.org/~pgj/patches/2013/10/29/porters-handbook.staging.diff [2] http://people.freebsd.org/~pgj/patches/2013/10/29/porters-handbook-staging/ That looks like a great improvement to the current state! -- 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
State of the Porters' Handbook
Neither staging nor license management are described in the Porters' Handbook. Why again should we bother to support it? What happened to the feature that is not documented doesn't exist? -- 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: State of the Porters' Handbook
On 28/10/2013 09:47, Łukasz Wąsikowski wrote: W dniu 2013-10-28 09:41, Dominic Fandrey pisze: Neither staging nor license management are described in the Porters' Handbook. Why again should we bother to support it? What happened to the feature that is not documented doesn't exist? Lack of good documentation is real problem for me to convert ports to staging. Porter's Handbook is seriously lagging behind recent changes - staging, license management, shabang fixes, etc. If it was up for a vote, I'd vote for a feature stop until the PH is back in a decent condition. Kudos to the people who documented the new options framework. -- 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: State of the Porters' Handbook
On 28/10/2013 09:58, John Marino wrote: On 10/28/2013 09:53, Dominic Fandrey wrote: On 28/10/2013 09:47, Łukasz Wąsikowski wrote: W dniu 2013-10-28 09:41, Dominic Fandrey pisze: Neither staging nor license management are described in the Porters' Handbook. Why again should we bother to support it? What happened to the feature that is not documented doesn't exist? Lack of good documentation is real problem for me to convert ports to staging. Porter's Handbook is seriously lagging behind recent changes - staging, license management, shabang fixes, etc. If it was up for a vote, I'd vote for a feature stop until the PH is back in a decent condition. Kudos to the people who documented the new options framework. For all intents and purposes - licensing feature doesn't exist. The same issues you are raising have been raised before. Apparently the full licensing infrastructure is still lacking so it's in some kind of limbo. However, converting to stagedir is reasonably documented here: https://wiki.freebsd.org/ports/StageDir That's a handfull. What about installers that hard-code directories during install? You don't have a choice with supporting stage -- new ports without stage aren't accepted. So that's why you have to bother. :) That doesn't sound acceptable, considering the feature isn't even mentioned in the Porters' Handbook. -- 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: State of the Porters' Handbook
On 28/10/2013 10:34, John Marino wrote: On 10/28/2013 10:29, Dominic Fandrey wrote: On 28/10/2013 09:58, John Marino wrote: On 10/28/2013 09:53, Dominic Fandrey wrote: However, converting to stagedir is reasonably documented here: https://wiki.freebsd.org/ports/StageDir That's a handfull. What about installers that hard-code directories during install? They can hardcode into the stage directory. Anywhere else is wrong and has to be fixed. But then they won't be usable once installed into /usr/local. You don't have a choice with supporting stage -- new ports without stage aren't accepted. So that's why you have to bother. :) That doesn't sound acceptable, considering the feature isn't even mentioned in the Porters' Handbook. Bapt has made several calls for help to document this in the Porters Handbook. He's said it's on his plate but he's behind and has asked for the help. Maybe you could help him out? So far I see stage as a problem, not something I want to advance. -- 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: State of the Porters' Handbook
On 28/10/2013 11:03, John Marino wrote: On 10/28/2013 10:54, Dominic Fandrey wrote: On 28/10/2013 10:34, John Marino wrote: On 10/28/2013 10:29, Dominic Fandrey wrote: That's a handfull. What about installers that hard-code directories during install? They can hardcode into the stage directory. Anywhere else is wrong and has to be fixed. But then they won't be usable once installed into /usr/local. If there are files in those directories, they'll be on the plist and stage handles them. I'd have to look up how to create empty directories properly. Stage replaceses strings in installed files? You don't have a choice with supporting stage -- new ports without stage aren't accepted. So that's why you have to bother. :) That doesn't sound acceptable, considering the feature isn't even mentioned in the Porters' Handbook. Bapt has made several calls for help to document this in the Porters Handbook. He's said it's on his plate but he's behind and has asked for the help. Maybe you could help him out? So far I see stage as a problem, not something I want to advance. I don't know how to respond to this. 1. It indicates that don't understand the benefits, nor that it's 5 years overdue, nor that its sorely needed I can see the benefits for less error prone package building. But right now it's just additional work coming my way. 2. Stage is not going away. There is not another option. 3. You've been given a source of documentation. It's not in the handbook, but it does exist in some form. What more do you need to progress? There is a procedure. Stuff belongs into the handbook. Stick to it. -- 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: State of the Porters' Handbook
On 28/10/2013 11:26, John Marino wrote: On 10/28/2013 11:16, Dominic Fandrey wrote: On 28/10/2013 11:03, John Marino wrote: If there are files in those directories, they'll be on the plist and stage handles them. I'd have to look up how to create empty directories properly. Stage replaceses strings in installed files? No, the port does that kind of thing in the stage directory. After everything is installed there in the stage directory, they are packaged or installed into the $PREFIX I can see the benefits for less error prone package building. But right now it's just additional work coming my way. You really need to get a better grasp of the concept. There are several emails from bapt that may help. For new ports it's not additional work and for existing ports, yes there is a conversion but the benefits are worth it. 2. Stage is not going away. There is not another option. 3. You've been given a source of documentation. It's not in the handbook, but it does exist in some form. What more do you need to progress? There is a procedure. Stuff belongs into the handbook. Stick to it. Fine, but it's a huge topic that somebody has to write and validate. You're willing to criticize (justified) but unwilling to help rectify the problem. Well, bsd.stage.mk isn't well commented either. I think right now only the person who implemented it could write reasonable documentation. If you only want to complain, I think you've made your point (a point that everyone is already aware of). FYI, I have no dog in the hunt other than I believe stage is a welcome update to ports. 1. Implementation 2. Testing 3. Documentation 4. Mandatory We're in stage 2 and it's already mandatory. I'm not against staging, I'm against making things prematurely mandatory. -- 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] Update of xorg libraries and MESA
On 09/09/2013 16:52, Niclas Zeising wrote:
On 09/09/13 14:49, Niclas Zeising wrote:
[Cross-posted between x11@ and ports@, please respect reply-to]
Hi!
It is time once again to update parts of the FreeBSD xorg stack, and the
x11@ team needs YOUR help in testing!
Build of graphics/dri fails on stable/9:
FreeBSD mobileKamikaze.norad 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0 r254957:
Tue Aug 27 19:07:40 CEST 2013
root@mobileKamikaze.norad:/usr/obj/HP6510b-9/amd64/usr/src/sys/HP6510b-9 amd64
The ports tree is up to date, so is the patch (just fetched).
CC intel_screen.lo
clang: warning: argument unused during compilation: '-fno-builtin-memcmp'
clang: warning: argument unused during compilation: '-fno-builtin-memcmp'
intel_context.c:1026:14: warning: unused variable 'max_attachments'
[-Wunused-variable]
const int max_attachments = ARRAY_SIZE(attachments) / 2;
^
intel_screen.c:199:6: error: use of undeclared identifier
'__DRI_IMAGE_FOURCC_ARGB'
{ __DRI_IMAGE_FOURCC_ARGB, __DRI_IMAGE_COMPONENTS_RGBA, 1,
^
intel_screen.c:199:35: error: use of undeclared identifier
'__DRI_IMAGE_COMPONENTS_RGBA'
{ __DRI_IMAGE_FOURCC_ARGB, __DRI_IMAGE_COMPONENTS_RGBA, 1,
^
intel_screen.c:202:6: error: use of undeclared identifier
'__DRI_IMAGE_FOURCC_XRGB'
{ __DRI_IMAGE_FOURCC_XRGB, __DRI_IMAGE_COMPONENTS_RGB, 1,
^
intel_screen.c:202:35: error: use of undeclared identifier
'__DRI_IMAGE_COMPONENTS_RGB'
{ __DRI_IMAGE_FOURCC_XRGB, __DRI_IMAGE_COMPONENTS_RGB, 1,
^
intel_screen.c:205:6: error: use of undeclared identifier
'__DRI_IMAGE_FOURCC_YUV410'
{ __DRI_IMAGE_FOURCC_YUV410, __DRI_IMAGE_COMPONENTS_Y_U_V, 3,
^
1 warning generated.
CC intel_span.lo
intel_screen.c:205:33: error: use of undeclared identifier
'__DRI_IMAGE_COMPONENTS_Y_U_V'
{ __DRI_IMAGE_FOURCC_YUV410, __DRI_IMAGE_COMPONENTS_Y_U_V, 3,
^
clang: warning: argument unused during compilation: '-fno-builtin-memcmp'
intel_screen.c:206:19: error: use of undeclared identifier
'__DRI_IMAGE_FORMAT_R8'
{ { 0, 0, 0, __DRI_IMAGE_FORMAT_R8, 1 },
^
intel_screen.c:207:19: error: use of undeclared identifier
'__DRI_IMAGE_FORMAT_R8'
{ 1, 2, 2, __DRI_IMAGE_FORMAT_R8, 1 },
^
intel_screen.c:208:19: error: use of undeclared identifier
'__DRI_IMAGE_FORMAT_R8'
{ 2, 2, 2, __DRI_IMAGE_FORMAT_R8, 1 } } },
^
intel_screen.c:210:6: error: use of undeclared identifier
'__DRI_IMAGE_FOURCC_YUV411'
{ __DRI_IMAGE_FOURCC_YUV411, __DRI_IMAGE_COMPONENTS_Y_U_V, 3,
^
intel_screen.c:210:33: error: use of undeclared identifier
'__DRI_IMAGE_COMPONENTS_Y_U_V'
{ __DRI_IMAGE_FOURCC_YUV411, __DRI_IMAGE_COMPONENTS_Y_U_V, 3,
^
intel_screen.c:211:19: error: use of undeclared identifier
'__DRI_IMAGE_FORMAT_R8'
{ { 0, 0, 0, __DRI_IMAGE_FORMAT_R8, 1 },
^
intel_screen.c:212:19: error: use of undeclared identifier
'__DRI_IMAGE_FORMAT_R8'
{ 1, 2, 0, __DRI_IMAGE_FORMAT_R8, 1 },
^
intel_screen.c:213:19: error: use of undeclared identifier
'__DRI_IMAGE_FORMAT_R8'
{ 2, 2, 0, __DRI_IMAGE_FORMAT_R8, 1 } } },
^
CC intel_state.lo
intel_screen.c:215:6: error: use of undeclared identifier
'__DRI_IMAGE_FOURCC_YUV420'
{ __DRI_IMAGE_FOURCC_YUV420, __DRI_IMAGE_COMPONENTS_Y_U_V, 3,
^
intel_screen.c:215:33: error: use of undeclared identifier
'__DRI_IMAGE_COMPONENTS_Y_U_V'
{ __DRI_IMAGE_FOURCC_YUV420, __DRI_IMAGE_COMPONENTS_Y_U_V, 3,
^
intel_screen.c:216:19: error: use of undeclared identifier
'__DRI_IMAGE_FORMAT_R8'
{ { 0, 0, 0, __DRI_IMAGE_FORMAT_R8, 1 },
^
clang: warning: argument unused during compilation: '-fno-builtin-memcmp'
intel_screen.c:217:19: error: use of undeclared identifier
'__DRI_IMAGE_FORMAT_R8'
{ 1, 1, 1, __DRI_IMAGE_FORMAT_R8, 1 },
^
intel_screen.c:218:19: error: use of undeclared identifier
'__DRI_IMAGE_FORMAT_R8'
{ 2, 1, 1, __DRI_IMAGE_FORMAT_R8, 1 } } },
^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
gmake[6]: *** [intel_screen.lo] Error 1
gmake[6]: *** Waiting for unfinished jobs
gmake[6]: Leaving directory
`/tmp/obj/mobileKamikaze.norad/amd64/usr/ports/graphics/dri/work/Mesa-9.1.6/src/mesa/drivers/dri/i915'
gmake[5]: *** [all-recursive] Error 1
gmake[5]: Leaving directory
`/tmp/obj/mobileKamikaze.norad/amd64/usr/ports/graphics/dri/work/Mesa-9.1.6/src/mesa/drivers/dri'
gmake[4]: *** [all-recursive] Error 1
gmake[4]: Leaving directory
`/tmp/obj/mobileKamikaze.norad/amd64/usr/ports/graphics/dri/work/Mesa-9.1.6/src/mesa/drivers'
gmake[3]: *** [all-recursive] Error 1
gmake[3]: Leaving directory
License framework
A lot of maintainers seem to have tested the license framework and recently a committer even added license information while committing one of my updates. My stand on it is that I don't care enough to be a beta-tester for it and that I'll pick up the practice, once it's described in the Porters' Handbook. Which it isn't. Why is that? -- 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
xpi-* broken since firefox-22
I don't know whether that's a general problem or just affects me, but since Firefox 22 the xpi-* ports don't work for me any more. I.e. they install just fine, but firefox doesn't pick them up. I'm a huge fan of everything goes into the package system and I am convinced plugin systems and automatic updates are just hacks that wouldn't even exist if Windows had a package system. But there simply are too many firefox addons and I think before anything gets fixed it's time to put down some hard rule for plugin/addon kind of stuff. My suggestion is the following: Any plugin/addon may be added to the ports collection if one or more of the following conditions are met: - The plugin/addon builds/contains native code - The plugin/addon is a dependency of another port - The plugin/addon improves the integration with the base system, .e.g. it adds support for common environment variables like LANG, HTTP_PROXY or TZ -- 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: xpi-* broken since firefox-22
On 26/08/2013 18:59, Florian Smeets wrote: On 26.08.13 14:07, Dominic Fandrey wrote: I don't know whether that's a general problem or just affects me, but since Firefox 22 the xpi-* ports don't work for me any more. This was broken for a brief period, it should be fixed though. You might need to reinstall the xpis so that the correct links are created. Thanks, when it happened I installed everything locally and that probably masks that the ports xpis work again. Any plugin/addon may be added to the ports collection if one or more of the following conditions are met: - The plugin/addon builds/contains native code - The plugin/addon is a dependency of another port - The plugin/addon improves the integration with the base system, .e.g. it adds support for common environment variables like LANG, HTTP_PROXY or TZ That's the plan anyway. I'm working on it. Enigmail and lightning will stay, perhaps the MOZILLA-xpi ports, but I'm leaning to removing those too, as they can be installed from addons.mozilla.org just fine. I'm just busy and haven't put this up for approval/discussion, yet. I'm maintainer of 2 xpi- ports. I'm willing to continue maintaining them if this is the verdict. But my vote is on getting rid of them. -- 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: sysutils/fusefs-ntfs fusefs_enable=YES
On 21/08/2013 23:39, RW wrote: The README.FreeBSD file for sysutils/fusefs-ntfs and several howtos suggest adding the line: fusefs_enable=YES to rc.conf, but as far as I can see this doesn't affect anything since the port doesn't install an rc.d file. I would have expected such a file to load the fuse kernel module which I'm having to load myself. The file is there. fusefs-kmod -- 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: Correct way to install preprocessed man pages
On 01/05/2013 14:29, Jake Smith wrote: I am putting a new port together, but the source for the man pages is not provided in the source tar for the package (and I can't find a public repo). Instead only the preprocessed version is included. Do you mean it's already compressed or it's already formatted? That would be odd, because I think that should tie in with TERM and PAGER. So it must be considered broken by design. Regards -- 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
[CFT] sysutils/automounter 1.4.5
I have run into a devd race with automounter on recent stable/9. Changed devd behaviour causes fork bomb like behaviour under certain conditions. If you are willing to help, please download: https://sourceforge.net/p/bsdadminscripts/automounter/ci/tip/tarball And run the following commands as a super user: tar -xf bsdadminscripts-automounter-tip.zip cd bsdadminscripts-automounter-tip/src/ ./install.sh service devd restart Due to the severity of the situation the scheduled release date is the 3rd May, the day after tomorrow. Regards -- 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: libreoffice
On 18/02/2013 12:46, Wojciech Puchar wrote: package works great (and far faster than openoffice) but still i would find quickstarter functionality that is available in windows openoffice useful. You know that time a quickstarter saves you starting a program is just the same time it made your system start take longer. Quick starters are a huge part of the reason windows installations start to feel sluggish after some time. They are a plague, binding resources before it's even clear that they're needed. Why MS accepted this practice from software vendors is beyond me. They accept that their system looks bad on behalf of making the software it runs look good, without any real benefit to the user. It's just about shifting blame. -- 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: libreoffice
On 21/02/2013 20:54, Wojciech Puchar wrote: You know that time a quickstarter saves you starting a program is just the same time it made your system start take longer. true. but if user close a document and then open another - you get twice the waiting time. That's strange. As long as you've got enough RAM all the data should remain cached. A successive start of libreoffice takes 1s on my system. Only the first start gives me a couple of seconds of hard disk activity. -- 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: New version of TeX?
On 16/02/2013 18:31, Chris Rees wrote: On 6 February 2013 13:50, Nathan Whitehorn nwhiteh...@freebsd.org wrote: On 02/05/13 21:01, Dominic Fandrey wrote: On 04/02/2013 21:08, Boris Samorodov wrote: 04.02.2013 10:21, Dominic Fandrey пишет: On 04/02/2013 02:04, Danilo Egea wrote: Well, there is this project http://code.google.com/p/freebsd-texlive/ http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/171571 I use the patch from this PR together with the attached diff and portmaster seems to DTRT with dependencies. Seeing that someone else actually uses it, I just attached a little update fixing a problem I discovered only a couple of days ago. I recommend you to install texlive-base again. Also I think it would be nice if you attached your patches to the PR. Regards Is there any chance this could be committed now pending a longer-term rearchitecture of the TeX stuff? I just installed it on three machines (thanks!) with no trouble at all and everything is working perfectly. Waiting for some long-term solution seems to be making the perfect the enemy of the good -- and this Friday will mark 8 years since the last teTeX update. I would very much like to put Dominic's version in (for no particular reason other than simplicity, and it was the first I looked at-- I can't see any major advantage of one over the other). It would be nice to have it, however it's not yet in a state to /replace/ teTeX. So far it's only an alternative. I'd still have to make a real conflicts test and take care of the most common teTeX depending ports in a way that doesn't cause the entire texlive-texmf to be pulled in as a dependency. I won't be able to work on this sooner than 1 month from now. -- 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: LibreOffice 3.6.5 on amd
On 08/02/2013 14:41, Albert Shih wrote: === Registering installation for libreoffice-3.6.5_1 pkg_create: read_plist: unknown command '@dirrmtry share/mimelnk/application' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/mimelnk' (package tools out of date?) pkg_create: read_plist: unknown command '@dirrmtry share/mime/packages' (package tools out of date?) ... Any idea ? I thought I somehow had my tinderbox jails polluted by creating legacy and pkgng builds from the same jails. I just removed all my jails to start from scratch, because of that. And all the packages, because I suspected they were created with a mixed set of pkg-tools. Ouch. This mess is going to compile for a couple of days. :D -- 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: New version of TeX?
On 04/02/2013 21:08, Boris Samorodov wrote: 04.02.2013 10:21, Dominic Fandrey пишет: On 04/02/2013 02:04, Danilo Egea wrote: Well, there is this project http://code.google.com/p/freebsd-texlive/ http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/171571 I use the patch from this PR together with the attached diff and portmaster seems to DTRT with dependencies. Seeing that someone else actually uses it, I just attached a little update fixing a problem I discovered only a couple of days ago. I recommend you to install texlive-base again. Also I think it would be nice if you attached your patches to the PR. Regards -- 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: If a port requires xorg-server's source tree, how to write Makefile?
On 03/02/2013 13:30, meta wrote:
Hi,
A few times I've already posted freebsd-ports list that I'm working for
creating a port net/tigervnc. It is almost be done but I have a question.
TigerVNC's source tree is not complete to make everything. We have to
put freebsd-patched xorg-server's source tree into its tree. I tried
like this. It builds fine with WITH_NEW_XORG and old xorg.
Is this a bad idea? Should I take another way?
post-extract:
${MAKE} -C ../../x11-servers/xorg-server patch
${CP} -R ../../x11-servers/xorg-server/work/xorg-server-${XORG_VERSION}/* \
${WRKSRC}/unix/xserver/
post-clean:
${MAKE} -C ../../x11-servers/xorg-server clean
BUILD_DEPENDS= ${NONEXISTENT}:${PORTSDIR}/x11-servers/xorg-server:extract
See the Porters' Handbook section 5.8.
Regards
--
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: libreoffice build fails on i386
On 03/02/2013 05:08, Kevin Oberman wrote: I am unable to build libreoffice on an i386 system. It builds fine on amd64. All systems are running 9.1-stable, one from Jan. 10 and one from Jan. 27. Both using default compilers. I get a segment fault running the sot. This may not be a solution to your build problem. But I can offer you libreoffice packages: http://wiki.bsdforen.de/anwendungen/libreoffice_aus_inoffiziellen_paketen#freebsd_amd64i386_918374-releng_kamikaze -- 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: New version of TeX?
On 04/02/2013 02:04, Danilo Egea wrote: Well, there is this project http://code.google.com/p/freebsd-texlive/ http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/171571 -- 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: E17 won't start
On 24/12/2012 10:57, Grzegorz Blach wrote: On Mon, 2012-12-24 at 03:46 +0100, Dominic Fandrey wrote: On 24/12/2012 03:28, Dominic Fandrey wrote: On 24/12/2012 03:19, Dominic Fandrey wrote: On 23/12/2012 20:18, Matthieu Volat wrote: I've been unable to start an enlightenment session after the recent upgrade to the release. I managed to fix it by building all evas-* packages with base gcc! I rebuilt all EFL and E17 with clang and I get black screen issue, but E17 start to work after I rebuilt only evas-core with gcc. Can anyone confirm that, building evas-core with gcc fixes this issue. I rebuilt everything with clang except for evas-core. It still works, so yes rebuilding evas-core with gcc is the fix/workaround. -- 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: E17 won't start
On 23/12/2012 20:18, Matthieu Volat wrote: I've been unable to start an enlightenment session after the recent upgrade to the release. I have the same issue. I just have a black screen with the mouse (that can move) and nothing else. There is nothing that can help in ~/.xession-errors... Well it's noteworthy that after the first ESTART: SLEEP message I've got a line that says PAUSE !. As far as I can figure this is unusual. If there's anything /unusual/ in my install, it's that all ports that can be built witch clang, were built with clang. -- 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: E17 won't start
On 24/12/2012 03:19, Dominic Fandrey wrote: On 23/12/2012 20:18, Matthieu Volat wrote: I've been unable to start an enlightenment session after the recent upgrade to the release. I have the same issue. I just have a black screen with the mouse (that can move) and nothing else. There is nothing that can help in ~/.xession-errors... Well it's noteworthy that after the first ESTART: SLEEP message I've got a line that says PAUSE !. As far as I can figure this is unusual. If there's anything /unusual/ in my install, it's that all ports that can be built witch clang, were built with clang. I just ran it in gdb. But gdb reports a series of signals: SIGTRAP SIGTRAP SIGTTIN SIGTRAP Now, finally the startup procedures are executed until: ESTART: 0.34318 [0.1] - Manage all windows ESTART: 0.36315 [0.01997] - MAIN LOOP AT LAST ESTART: 0.64266 [0.27951] - SLEEP at which point gdb catches a SIGSEV! If I continue from here I end up with the single PAUSE ! line and nothing at all happens from here on. -- 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: E17 won't start
On 24/12/2012 03:28, Dominic Fandrey wrote: On 24/12/2012 03:19, Dominic Fandrey wrote: On 23/12/2012 20:18, Matthieu Volat wrote: I've been unable to start an enlightenment session after the recent upgrade to the release. I have the same issue. I just have a black screen with the mouse (that can move) and nothing else. There is nothing that can help in ~/.xession-errors... Well it's noteworthy that after the first ESTART: SLEEP message I've got a line that says PAUSE !. As far as I can figure this is unusual. If there's anything /unusual/ in my install, it's that all ports that can be built witch clang, were built with clang. I just ran it in gdb. But gdb reports a series of signals: SIGTRAP SIGTRAP SIGTTIN SIGTRAP Now, finally the startup procedures are executed until: ESTART: 0.34318 [0.1] - Manage all windows ESTART: 0.36315 [0.01997] - MAIN LOOP AT LAST ESTART: 0.64266 [0.27951] - SLEEP at which point gdb catches a SIGSEV! If I continue from here I end up with the single PAUSE ! line and nothing at all happens from here on. I managed to fix it by building all evas-* packages with base gcc! -- 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: gcc and g++ version setting in buildflags.conf
On 16/12/2012 08:26, Beeblebrox wrote: I am running a purely clang world (no gcc42), while I also have gcc46 installed for ports building. I use ccache for both world and ports. In /usr/local/etc/buildflags.conf I have set: BUILDFLAGS_GCC= 4.6+ GCC_DEFAULT_VERSION=4.6+ # USE_GCC=4.6+ # breaks distcc Some ports builds unfortunately break under this setup because build is looking for world's cc (gcc42 or clang). If I do this below, then the build completes fine: # setenv cc gcc46 setenv cxx g++46 BUILDFLAGS_GCC takes effect if WITH_GCC is defined and the port being compiled does not set CC/CXX itself. For more information see buildflags.mk(1). -- 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] fusefs-ntfs and fusefs-libs updates
On 24/10/2012 15:33, Florian Smeets wrote: On 10/22/2012 10:05, Dominic Fandrey wrote: On my RELENG_9 system apart from ntfs non of the fusefs systems works any more: fusefs-smbnetfs-0.5.3a fusefs-sshfs-2.4 fusefs-wdfs-1.4.2_4 And concerning ntfs, ports/170695 is still present. All in all, I was much better off before the updates. Yes, I'm aware of the problems. We are working on making the fuse import from head work on older releases and update the fusefs-kmod with that. Also we are currently looking into the problem why certain fusefs filesystems don't work with the current versions in ports. Oh, thanks! If you need me to test anything ... -- 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] fusefs-ntfs and fusefs-libs updates
On my RELENG_9 system apart from ntfs non of the fusefs systems works any more: fusefs-smbnetfs-0.5.3a fusefs-sshfs-2.4 fusefs-wdfs-1.4.2_4 And concerning ntfs, ports/170695 is still present. All in all, I was much better off before the updates. -- 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 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. Maybe I need to add texlive conflicts to teTeX and its ilk. I also want to add a texlive-asymptote port. But only after texlive is out there. I already tested the build, but there are some dependencies I want to add OPTIONS for and that's nothing I want to inflict on the texlive-base. -- 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 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 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 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: [CFT] TexLive port
Hi,
On 14/08/2012 03:49, Denny Lin wrote:
On Mon, Aug 13, 2012 at 09:50:15AM +0200, Dominic Fandrey wrote:
On 13/08/2012 04:45, Denny Lin wrote:
On Sun, Aug 12, 2012 at 10:12:33AM +0200, Dominic Fandrey wrote:
On 31/07/2012 00:48, Dominic Fandrey wrote:
Here we go:
http://www.home.hs-karlsruhe.de/~fado1011/texlive/
Adding this line to print/texlive-base/Makefile should remove the need
to patch graphics/poppler:
CFLAGS+= -I${LOCALBASE}/include
I still think this is a proplem of poppler, so it should be fixed
there. However, I agree the way I go about fixing it is not optimal.
So I have updated the patch. Still not satisfactory, but maybe a
little better.
texlinks: config file `fmtutil.cnf' not found.
Something must have gone wrong with texlive-texmf. The file should be
in ${LOCALBASE}/share/texmf/web2c/fmtutil.cnf
I tried searching for fmtutil.cnf:
# find work/texlive-20120701-source/ -name fmtutil.cnf
work/texlive-20120701-source/texk/tetex/fmtutil.cnf
This error occurs even when I patched poppler, so it should be unrelated
to the workaround mentioned above.
Maybe just try to wipe all the teTeX stuff and make a clean start
with print/texlive. It works in my Tinderbox, so the installation
procedure should be fine.
Ok, it seems that a few files were accidentally deleted in the process
of replacing teTeX with Tex Live. I reinstalled the Tex Live ports, and
the error disappeared.
Do you by any chance remember all the tetex related things you needed
to remove? I'd like to add them to CONFLICTS.
However, I noticed a problem with the symlinks in print/texlive-base.
For instance, /usr/local/bin/mktexfmt pointed to fmtutil at first, but
this line in post-install:
link=${LOCALBASE}/share/texmf$${link##*/texmf};
changed it to /usr/local/share/texmffmtutil. Not all the symlinks need
to be modified.
Thanks for that one, it didn't cause problems with doxygen or any of the
tex docs I have lying around, so I suppose this one was difficult to find.
I've attached a fix although it's not very elegant (everything worked as
expected after the symlinks were fixed).
Doing it that way was a bad idea from the start. You'll like the way
I do it in the updated patch better.
I also reworked texlive-texmf
to build the plist and install the files at the same time to make it run
faster.
That shouldn't be working, because generate-plist is run before
do-install. Run:
# pkg_info -Lx texlive-texmf
And check whether it lists any files.
Thanks for all the time and effort you put into porting Tex Live! It
would be great to see TeX Live replace teTeX, regardless of whose port
is used.
Yes, definitely!
--
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 13/08/2012 04:45, Denny Lin wrote:
Hi,
On Sun, Aug 12, 2012 at 10:12:33AM +0200, Dominic Fandrey wrote:
On 31/07/2012 00:48, Dominic Fandrey wrote:
Here we go:
http://www.home.hs-karlsruhe.de/~fado1011/texlive/
# mkdir ~/texlive
# cd ~/texlive
# fetch
http://www.home.hs-karlsruhe.de/~fado1011/texlive/patch-ports-graphics-poppler.txt
http://www.home.hs-karlsruhe.de/~fado1011/texlive/shar-ports-print-texlive.txt
# cd /usr
# patch ~/texlive/patch-ports-graphics-poppler.txt
# sh ~/texlive/shar-ports-print-texlive.txt
# portmaster graphics/poppler
Adding this line to print/texlive-base/Makefile should remove the need
to patch graphics/poppler:
CFLAGS+= -I${LOCALBASE}/include
If you don't have teTeX installed:
# portmaster print/texlive
If you have teTeX installed:
# portmaster -o print/texlive-texmf print/teTeX-texmf
# portmaster -o print/texlive-base print/teTeX-base
# portmaster -o print/texlive print/teTeX
This probably needs to be run before portmaster if teTeX is installed:
# pkg_delete -f 'dvipsk-tetex-*'
# pkg_delete -f 'xdvik-tetex-*'
print/texlive-base fails to build/install for some reason:
gmake[4]: Leaving directory
`/usr/ports/print/texlive-base/work/texlive-20120701-source/texk/texlive'
gmake[3]: Leaving directory
`/usr/ports/print/texlive-base/work/texlive-20120701-source/texk/texlive'
gmake[2]: Leaving directory
`/usr/ports/print/texlive-base/work/texlive-20120701-source/texk/texlive'
gmake[1]: Leaving directory
`/usr/ports/print/texlive-base/work/texlive-20120701-source/texk'
texlinks: config file `fmtutil.cnf' not found.
Something must have gone wrong with texlive-texmf. The file should be
in ${LOCALBASE}/share/texmf/web2c/fmtutil.cnf
I tried searching for fmtutil.cnf:
# find work/texlive-20120701-source/ -name fmtutil.cnf
work/texlive-20120701-source/texk/tetex/fmtutil.cnf
This error occurs even when I patched poppler, so it should be unrelated
to the workaround mentioned above.
Maybe just try to wipe all the teTeX stuff and make a clean start
with print/texlive. It works in my Tinderbox, so the installation
procedure should be fine.
--
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
[CFT] TexLive port
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/ # mkdir ~/texlive # cd ~/texlive # fetch http://www.home.hs-karlsruhe.de/~fado1011/texlive/patch-ports-graphics-poppler.txt http://www.home.hs-karlsruhe.de/~fado1011/texlive/shar-ports-print-texlive.txt # cd /usr # patch ~/texlive/patch-ports-graphics-poppler.txt # sh ~/texlive/shar-ports-print-texlive.txt # portmaster graphics/poppler If you don't have teTeX installed: # portmaster print/texlive If you have teTeX installed: # portmaster -o print/texlive-texmf print/teTeX-texmf # portmaster -o print/texlive-base print/teTeX-base # portmaster -o print/texlive print/teTeX The texlive-texmf distfile is huge and ftp.tug.org is slow. If somebody knows any mirrors, please let me know! Regards -- 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
RELENG_7/amd64 feedback for devel/zziplib required
The port is marked broken for RELENG_7/amd64 for segfaulting during build. It doesn't segfault in my RELENG_9 hosted RELENG_7 Tinderbox jail: http://www.freebsd.org/cgi/query-pr.cgi?pr=170548 Can any of you native RELENG_7 users out there shed some light whether the issue exists on your boxes? My texlive-base port depends on devel/zziplib. Regards -- 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
Hello, On 12/08/2012 10:50, Baptiste Daroussin wrote: On Sun, Aug 12, 2012 at 10:12:33AM +0200, Dominic Fandrey wrote: ... Here we go: Are you aware of: http://code.google.com/p/freebsd-texlive/ ? romain@ has been working and maintaining those ports for a while and has plan to merge them into the ports tree once he is back from vacations (in about a month iirc) did you contact him? maybe both of your work can be merged? I know hrs@ also has/had? plan about texlive, merging the effort and plan could be good. Yes, I became aware when I tried to find out why there is no TeX Live port. I looked at it and dismissed it as more complicated than creating my own port. Our approaches are quite orthogonal. Whereas he uses the CTAN thingy to assemble all the parts that make up a TeX Live distribution, I simply grab the release tarballs and slab them onto the system. I expect both ports are pretty complete by now. I'd say I open the PR, he can submit his port for review into the same or another PR and we let the community discuss which is their preferred approach. His is definitely more fine grained and customizable, mine is probably easier to maintain. I'd be content with either solution so long as a TeX Live port makes it into the tree soon. It's always good to throw away stuff to make space for something better. So don't hesitate to declare my port inferior if that is your opinion. -- 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
TexLive port
I have a well working TexLive 2012 port, intended to be a replacement for teTex. I'm off to the FSAE Germany competition for a week, but afterwards I just have to make a couple of TB runs to weed out missing build dependencies and I can open the PR. Because a lot of things depend on a working TeX install I'd like to have some volunteers in a week. Regards, -- 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: Binary packages for LibreOffice 3.5 or 3.4
On 08/05/2012 08:53, Yamagi Burmeister wrote: I'd like to ask whether there are sites were binary packages could be downloaded from and are there any experiences with installing them on either 9-STABLE or 10-CURRENT? We (BSDForen.de) have unofficial packages build by the community at http://wiki.bsdforen.de/anwendungen/libreoffice_aus_inoffiziellen_paketen While the page is written in german, english (en_GB) packages are available. 7-STABLE, 8-STABE and 9-STABLE are covered. And the base version (without language packages) is always en_US. BTW, when our packages are a little late, this is normally for a reason. With the latest version it was the doc/docx issue. And of course there are a lot of packages to build. -- 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
libreoffice-3.5.2_1 tinderbox failure
There are a couple of issues that prevent tinderbox from creating tinderbox packages. The first issue, which prevents packaging on RELENG_9 is simply a wrong dependency path for x11-fonts/liberation-fonts-ttf. This one should be simple. On RELENG_8 and RELENG_9 tinderbox doesn't see the dependency on lang/clang. Thus the port installs it and tinderbox complains about an mtree error. I'm currently testing fixes for both. -- 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: libreoffice-3.5.2_1 tinderbox failure
On 24/04/2012 08:19, Dominic Fandrey wrote: On RELENG_8 and RELENG_9 tinderbox doesn't see the dependency on lang/clang. s/RELENG_9/RELENG_7/ -- 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: libreoffice-3.5.2_1 tinderbox failure
On 24/04/2012 09:10, Baptiste Daroussin wrote:
On Tue, Apr 24, 2012 at 08:19:49AM +0200, Dominic Fandrey wrote:
There are a couple of issues that prevent tinderbox from creating
tinderbox packages.
The first issue, which prevents packaging on RELENG_9 is simply a
wrong dependency path for x11-fonts/liberation-fonts-ttf. This one
should be simple.
On RELENG_8 and RELENG_9 tinderbox doesn't see the dependency on
lang/clang. Thus the port installs it and tinderbox complains about
an mtree error.
I'm currently testing fixes for both.
Thank is really strange to me, both passes my tinderboxes,
Concerning 9 it uses clang from base so it should need lang/clang, 8.2 should
automatically detect that it needs lang/clang and this works here
After fixing the liberation-fonts dep RELENG_9 builds.
But somehow the dependency on clang remains invisible to my tinderbox
for RELENG_8/7 builds. Whatever I do, it doesn't show up in the build
Makefile.
Maybe it's a bug in tinderbox and the creation of the file isn't
properly chrooted, but that seems rather unlikely.
for liberation-fonts-tff, looks strange, but I'll double check
That one is straightforward, the correct dependency is:
${LOCALBASE}/lib/X11/fonts/Liberation/LiberationMono-Bold.ttf
regards,
Bapt
--
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: libreoffice-3.5.2_1 tinderbox failure
On 24/04/2012 09:10, Baptiste Daroussin wrote: On Tue, Apr 24, 2012 at 08:19:49AM +0200, Dominic Fandrey wrote: There are a couple of issues that prevent tinderbox from creating tinderbox packages. ... On RELENG_8 and RELENG_7 (typo fixed) tinderbox doesn't see the dependency on lang/clang. Thus the port installs it and tinderbox complains about an mtree error. I'm currently testing fixes for both. Thank is really strange to me, both passes my tinderboxes, I renamed /usr/bin/clang in the host system and lo and behold the dependencies are picked up properly, so this is in deed a problem in TB and _not_ in the libreoffice port. Regards -- 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
Good source for linux libs
I need some linux libraries to throw in with a port of Eagle6. http://www.freebsd.org/cgi/query-pr.cgi?pr=164581 I'm Linux illiterate, does anyone know a good source for all of these: - libpng14.so.14 - libssl.so.1.0.0 - libcrypto.so.1.0.0 - libjpeg.so.8 With good source I mean something that qualifies as a respectable MASTER_SITE like some Linux distro that packs the right versions of the libraries. I'm afraid I might also need a different glibc version, but I'll burn that bridge when I cross it. -- 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: Update for graphics/ImageMagick failed
On 06/11/2011 08:27, Leslie Jensen wrote: Please take a look at this. CXXLD Magick++/lib/libMagick++.la CCLD utilities/animate magick/.libs/libMagickCore.so: undefined reference to `UnregisterPANGOImage' magick/.libs/libMagickCore.so: undefined reference to `RegisterPANGOImage' gmake[1]: *** [utilities/animate] Fel 1 gmake[1]: *** Inväntar oavslutade jobb... gmake[1]: Lämnar katalogen /usr/ports/graphics/ImageMagick/work/ImageMagick-6.7.3-3 gmake: *** [all] Fel 2 *** Error code 1 Stop in /usr/ports/graphics/ImageMagick. *** Error code 1 Stop in /usr/ports/graphics/ImageMagick. === make failed for graphics/ImageMagick === Aborting update === Update for graphics/ImageMagick failed === Aborting update I second this. -- 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: ports/162049: The Ports tree lacks a framework to restart services
On 31/10/2011 07:28, Doug Barton wrote: On 10/27/2011 09:27, Scott Lambert wrote: On Thu, Oct 27, 2011 at 11:15:00AM +0200, Ed Schouten wrote: What really bothers me when I use the FreeBSD Ports tree on one of my systems, is that the behaviour of dealing with services is quite inconsistent. If all of that is contingent upon a boolean knob the admin can set, something like NO_RESTART_SERVICES, I suspect everyone could get what they want and the bikeshed would be limitted to what the default for that boolean should be. The people who don't want the services restarted automagically can set it and, once things use the new ports framewoork properly, not have to worry about suprises. The people who want everything to restarted as soon as possible can set the knob the other way. I think Scott's on the right track. The way that I envision it working would be a 3-knob system. One knob to always restart the services, one to never do it; and then asking on a per-port basis, which should be the default. I can imagine portmaster detecting this option in the pre-build phase similarly to how it detects and warns about IS_INTERACTIVE now, and giving the user a menu of options for how to handle it. I'm happy to add more details if people are interested. I think this should be handled in the pkg-install script. Pkg based upgrade tools _do_ exist. Where this actually becomes interesting is not in the ports build/install process, which is pretty easy to deal with, but with package installs/deinstalls. I definitely think it's doable, what we probably want to do is put a knob for this in the port's Makefile, and handle the stop/start for both the port and the package with a little script that can be included in the package, and run with @exec and @unexec. Note the Porters' Handboock chapter 6.23.1. The knob to stop services is already there. hth, Doug -- 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: ports/162049: The Ports tree lacks a framework to restart services
On 31/10/2011 09:37, Doug Barton wrote: On 10/31/2011 00:38, Dominic Fandrey wrote: On 31/10/2011 07:28, Doug Barton wrote: On 10/27/2011 09:27, Scott Lambert wrote: On Thu, Oct 27, 2011 at 11:15:00AM +0200, Ed Schouten wrote: What really bothers me when I use the FreeBSD Ports tree on one of my systems, is that the behaviour of dealing with services is quite inconsistent. If all of that is contingent upon a boolean knob the admin can set, something like NO_RESTART_SERVICES, I suspect everyone could get what they want and the bikeshed would be limitted to what the default for that boolean should be. The people who don't want the services restarted automagically can set it and, once things use the new ports framewoork properly, not have to worry about suprises. The people who want everything to restarted as soon as possible can set the knob the other way. I think Scott's on the right track. The way that I envision it working would be a 3-knob system. One knob to always restart the services, one to never do it; and then asking on a per-port basis, which should be the default. I can imagine portmaster detecting this option in the pre-build phase similarly to how it detects and warns about IS_INTERACTIVE now, and giving the user a menu of options for how to handle it. I'm happy to add more details if people are interested. I think this should be handled in the pkg-install script. Pkg based upgrade tools _do_ exist. Yeah, that's what I said below. :) Sorry about that, I read the entire thread in one go, might have overlooked something. Ironic, because the purpose was to avoid posting redundant feedback. Where this actually becomes interesting is not in the ports build/install process, which is pretty easy to deal with, but with package installs/deinstalls. I definitely think it's doable, what we probably want to do is put a knob for this in the port's Makefile, and handle the stop/start for both the port and the package with a little script that can be included in the package, and run with @exec and @unexec. Note the Porters' Handboock chapter 6.23.1. The knob to stop services is already there. That feature as it exists currently isn't even close to adequate, and is causing more problems than it solves. Hence the discussion. Well, I am one of the people who see no need for this feature and my vote is for default off, if it's implemented. I just wanted to hint that such a function is already in place and I don't think it would be difficult to add the possibility to start a service. What has to be done after an update is often very specific, though. I don't envy the person having to come up with an adequate implementation. E.g. it's not always the service installed by the pkg that needs to be restarted: http://www.freebsd.org/cgi/cvsweb.cgi/ports/sysutils/automounter/pkg-message?rev=1.2;content-type=text%2Fplain Regards -- 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
bsd.clang.mk
I just submitted ports/162178 (http://www.freebsd.org/cgi/query-pr.cgi?pr=162178), it adds a bsd.clang.mk that allows port maintainers and users to tune the use of Clang/LLVM with the ports tree. Maintainers can: - Mark ports as CLANG_SAFE - Mark ports as CLANG_UNSAFE - Use CLANG_PREFERRED (if available, clang will be used instead of cc) - Use USE_CLANG (like CLANG_PREFERRED, but introduces a build dependency if clang originates from the ports tree) Users can: - PREFER_CLANG, which takes effect if a port is CLANG_SAFE - FORCE_CLANG, which takes effect unless a port is CLANG_UNSAFE Obviously this needs testers. The maintainer side is more complex, because you can do things like defining CLANG_UNSAFE=2.9- and CLANG_SAFE=3. It's also possible to define version ranges like USE_CLANG=2.9-3 or specify several ranges like CLANG_UNSAFE= 2.9- 3.4+. -- 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
enigmail 1.2
Hello, I got enigmail 1.2 to build by changing the gecko extract dependency target from configure to build. It installs and runs, but it always claims the gpg agent cannot be found. Even when I configure it manually. I'm out of ideas. Any suggestions? Regards -- 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: enigmail 1.2
OK, I got it, solution at the end.
On 05/07/2011 00:02, Matthias Andree wrote:
Am 04.07.2011 19:42, schrieb Dominic Fandrey:
Hello,
I got enigmail 1.2 to build by changing the gecko extract dependency
target from configure to build.
It installs and runs, but it always claims the gpg agent cannot
be found. Even when I configure it manually.
I'm out of ideas. Any suggestions?
Asking the obvious: do you have ${LOCALBASE}/bin/gpg-agent (from
security/gnupg)?
Yes.
...
The solution was to start gpg-agent and populate the
GPG_AGENT_INFO environment variable. The most convenient way for
me to do this was to change my .xsession:
exec /usr/local/bin/gpg-agent --daemon /usr/local/bin/mywm
Regards
--
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: cvs commit: ports UPDATING
On 01/07/2011 05:22, Doug Barton wrote: On 06/30/2011 14:03, Stephen Montgomery-Smith wrote: stephen 2011-06-30 21:03:43 UTC FreeBSD ports repository Modified files: .UPDATING Log: - Tell octave-forge* users to completely remove old ports before reinstalling. This is not the first time this issue (ports doing the wrong thing if you try to build them while they are installed) has come up, and I've been thinking ... do we need something like a NO_REINSTALL flag that can be added to a port's Makefile to indicate the problem? ... I think kdelibs3 has taken care of this by conflicting with itself. -- 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
openjdk7 missing dependency on alsa
My openjdk7 build fails building something named jsoundalsa. There's no alsa on my system and I don't see the dependency in the port. I installed audia/alsa-lib, now openjdk7 builds. Still I don't see why I need yet another sound server. Regards -- 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: problem building Firefox 4
Hello, On 24/03/2011 03:14, Robert Huff wrote: On FreeBSD 9.0-CURRENT #0: Sat Oct 23 08:15:53 EDT 2010 amd64 I get: ... /data/port-work/mozilla-2.0/obj-amd64-unknown-freebsd9.0/config/nsinstall -R -m 644 _xpidlgen/exthelper.xpt ../../../dist/bin/components Traceback (most recent call last): File /usr/local/lib/python2.7/site.py, line 62, in module import os File /usr/local/lib/python2.7/os.py, line 49, in module import posixpath as path File /usr/local/lib/python2.7/posixpath.py, line 16, in module import genericpath File /usr/local/lib/python2.7/genericpath.py, line 5, in module KeyboardInterrupt ... my guess is you have activated PGO and the build cannot access you Xorg session. Make sure Xorg is running, DISPLAY is set and the building user has the permissions to use Xorg. Regards, Kami -- 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
Firefox4 Ignores DPI
Firefox4 ignores both the system DPI setting and its own preference layout.css.dpi. Instead Firefox4 renders everything as if the screen had 96DPI. Here you can view the DPI used by your browser: http://www.home.hs-karlsruhe.de/~fado0001/testdpi.html I have submitted a fix to bugzilla.mozilla.org: https://bugzilla.mozilla.org/show_bug.cgi?id=603880#c5 The patch can be dropped into www/firefox/files/ as is. I would appreciate feedback. Regards, Kami -- 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
curses update
It seems a lot of dependant packages need to be rebuilt: # pkg_libchk aalib-1.4.r5_5: /usr/local/bin/aafire misses libncurses.so.5.7 aalib-1.4.r5_5: /usr/local/bin/aafire misses libncurses.so.5.7 aalib-1.4.r5_5: /usr/local/bin/aainfo misses libncurses.so.5.7 aalib-1.4.r5_5: /usr/local/bin/aainfo misses libncurses.so.5.7 aalib-1.4.r5_5: /usr/local/bin/aasavefont misses libncurses.so.5.7 aalib-1.4.r5_5: /usr/local/bin/aasavefont misses libncurses.so.5.7 aalib-1.4.r5_5: /usr/local/bin/aatest misses libncurses.so.5.7 aalib-1.4.r5_5: /usr/local/bin/aatest misses libncurses.so.5.7 aalib-1.4.r5_5: /usr/local/lib/libaa.so.1 misses libncurses.so.5.7 ... This is my personal rebuild list: # pkg_libchk -q aalib-1.4.r5_5 aspell-0.60.6_5 eclipse-3.6.1_1 gegl-0.1.6 gettext-0.18.1.1 gimp-app-2.6.11_2,1 gnuplot-4.4.0 gutenprint-base-5.2.4_2 input-wacom-40.0.8.2.2_6 irssi-0.8.15_2 libcaca-0.99.b17_3 libcdio-0.82_1 mencoder-1.0.r20101106_1 mjpegtools-1.9.0_2 mplayer-1.0.r20101106_1 octave-3.2.4_4 opera-11.01 pinentry-gtk2-0.8.1 python26-2.6.6 rtorrent-0.8.7 ruby-1.8.7.302,1 samba34-3.4.9_2 sdl-1.2.14_2,2 sdl_gfx-2.0.21_1 sdl_image-1.2.10_2 sdl_mixer-1.2.11_2 sdl_sound-1.0.3_4 smpeg-0.4.4_8 xmlrpc-c-devel-1.25.3 Regards -- 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: curses update
On 06/03/2011 21:17, Dominic Fandrey wrote: It seems a lot of dependant packages need to be rebuilt: This is my personal rebuild list: # pkg_libchk -q aalib-1.4.r5_5 aspell-0.60.6_5 eclipse-3.6.1_1 Sorry about getting eclipse in there. It showed up because it's linked against libjawt.so and that is not in the library path. Regards -- 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: xf86-video-ati 6.14.0 crashes System
On 27/02/2011 23:05, David Demelier wrote: On 27/02/2011 21:50, Christian Weisgerber wrote: Christoph Moench-Tegederc...@burggraben.net wrote: after update tu the new xorg on my FreeBSD8 my system crashes all time I start X. Same here with Also reported by me for the ATI Radeon RV370 X300 SE and somebody else for a differently branded card with the same chip. When using the ati/radeon driver, the system crashes too fast to leave any log (literally, Xorg.0.log was not changed), so I can't provide any information from there. Yup. As a workaround, install the version 6.13 driver. A separate port has been created for it. # portupgrade -o x11-drivers/xf86-video-ati613 xf86-video-ati That's sad, yet another panic :(. This time that's me who is lucky. I've got a radeon 4330 and it's working absolutely fine. Just to put this thread into context, the new driver improves the situation for some people, of course you don't see them complaining here. My machine has 2 ATI cards, one onboard (HD4200) and one in the PCIE slot (HD5770). The new driver allows me to switch back to the console when using the HD5770. In conjunction with the Xorg upgrade a reproducible panic with certain combinations of BIOS and xorg.conf configurations disappeared. These combinations still don't work, but instead of panicking the system, the Xorg process can be killed and the xorg.conf can be changed to a working configuration without a reboot or risk of data loss. Regards -- 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
webspace for libbluray and libaacs required
During the last 2 days I have ported libbluray and libaacs to FreeBSD. Installing them and rebuilding mplayer or vlc should allow playing blu-ray disks with the following constraints: - mount_udf must be able to mount the disk or the data must be copied to a hard disk by other means, first - The data must not be bd+ protected, the libbdplus source code is not available to the public - If the data is AACS encrypted a key file with required keys must be placed in ~/.dvdcss/KEYDB.cfg I don't have any blu-rays without bd+ restrictions, so all this is not tested. Currently I'm in need of webspace for the GIT snapshots to file a PR with the ports. Regards -- 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: What ports require this port?
On 07/02/2011 21:13, Dan Langille wrote: On Mon, February 7, 2011 11:06 am, Dominic Fandrey wrote: On 07/02/2011 03:01, b. f. wrote: Over the weekend, a new feature was added to FreshPorts BETA. A port now lists all ports that require it. This code will eventually move to production after it's been running on on the beta site for a while. Notes: * The code uses the output of make -V RUN_DEPENDS -V LIB_DEPENDS -V BUILD_DEPENDS If you're going to include BUILD_DEPENDS, then you should also use -V PATCH_DEPENDS -V FETCH_DEPENDS. Maybe it should be split into The package requires only listing the INSTALL_DEPENDS and The port requires listing all dependencies. Your post, combined with new information, has raised a question. Consider 'make build-depends-list' and 'make run-depends-list' for devel/glib20: $ make build-depends-list /usr/ports/devel/gettext ... $ make run-depends-list /usr/ports/devel/gettext ... ... I am tempted to alter FreshPorts and abandon all *_DEPENDS and use just run-depends-list and build-depends-list. How much value is there is having all of this information separated into individual _DEPENDS? The value is mostly for ports maintainers, commiters and tool developers i.e. those who develop pointyhat, tinderbox, portmaster or my little project pkg_upgrade. I think the relevant question is, which information is needed by the freshports users. The way I see it there are two relevant user groups, those who use packages and those who build packages. The first group only needs the run-depends, the second group needs the combined run- and build-depends. So I think those two lists is exactly what you need. I don't see added value for the end user in providing more fine grained information. Regards -- 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: What ports require this port?
On 07/02/2011 03:01, b. f. wrote: Over the weekend, a new feature was added to FreshPorts BETA. A port now lists all ports that require it. This code will eventually move to production after it's been running on on the beta site for a while. Notes: * The code uses the output of make -V RUN_DEPENDS -V LIB_DEPENDS -V BUILD_DEPENDS If you're going to include BUILD_DEPENDS, then you should also use -V PATCH_DEPENDS -V FETCH_DEPENDS. Maybe it should be split into The package requires only listing the INSTALL_DEPENDS and The port requires listing all dependencies. Regards -- 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: Plans for making MAKE_JOBS_SAFE as default
This is a resend, because I forgot to CC ports.
On 23/12/2010 10:18, Alexey Dokuchaev wrote:
Hi there,
As far as I remember, when _MAKE_JOBS functionality was introduced, one
of the ultimate goals was to flip the switch at some point so ports are
built with -jX unless marked as MAKE_JOBS_UNSAFE. What is current
situation and consensus? Are we ready for that? If not, what is
preventing us to do so? Is there some road-map, plan, or time frame?
I'd really like to see that happen. If there is anything I can help
with, don't hesitate to ask. :-)
Me too. This is my list of things that don't work with
FORCE_MAKE_JOBS, considering the number of packages on my
system it's pretty short. It might be incomplete,
or contain entries that no longer cause problems:
archivers/p7zip
audio/cdparanoia
audio/nas
converters/libiconv
devel/autoconf261
devel/doxygen
devel/gperf
devel/gobject-introspection
devel/icu
devel/libthai
devel/nasm
devel/ncurses
devel/ORBit2
devel/pth
dns/libidn
editors/vim
games/ultimatestunts
graphics/ImageMagick
graphics/libafterimage{!FORCE_MAKE_JOBS}
graphics/libart_lgpl
graphics/pstoedit
java/openjdk*
java/eclipse
multimedia/mplayer
multimedia/mencoder
net/mDNSResponder
print/ghostscript*
security/nss
security/cyrus-sasl2
textproc/jade
--
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: confused build_depends
On 02/12/2010 19:49, Olli Hauer wrote: On 2010-12-02 14:12, Dominic Fandrey wrote: # cd /usr/ports/net/wireshark # make -VBUILD_DEPENDS /usr/local/lib/libcrypto.so.8:/usr/ports/cad/linux-eagle5 ... Well, eagle5 does not install the file libcrypto.so.8, thus it doesn't exist and the ports system will try to install linux-eagle5 when building wireshark. Of course linux-eagle5 is already installed, thus it will fail. If I remove linux-eagle5 the dependency works: # make -VBUILD_DEPENDS /usr/local/lib/libcrypto.so.7:/usr/ports/security/openssl ... But why does the ports system think linux-eagle installs this library? # pkg_info -Lx eagle|grep crypto /compat/linux/lib/libcrypto.so.0.9.8 The file is a symlink and has a distinctively different version number. Are you sure you are in the wireshark port? I cannot find a reference to linux-eagle5, even in older versions. http://www.freebsd.org/cgi/cvsweb.cgi/ports/net/wireshark/Makefile?annotate=1.161 It affects everything depending on libcrypto. If dependency file exists, the ports system will substitute the package that installed it for the dependency set in the port. It's something in bsd.port.mk that goes wrong and /thinks/ linux-eagle5 installs a file that it actually doesn't. Install linux-eagle5 and you can reproduce it. Regards -- 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
confused build_depends
# cd /usr/ports/net/wireshark # make -VBUILD_DEPENDS /usr/local/lib/libcrypto.so.8:/usr/ports/cad/linux-eagle5 ... Well, eagle5 does not install the file libcrypto.so.8, thus it doesn't exist and the ports system will try to install linux-eagle5 when building wireshark. Of course linux-eagle5 is already installed, thus it will fail. If I remove linux-eagle5 the dependency works: # make -VBUILD_DEPENDS /usr/local/lib/libcrypto.so.7:/usr/ports/security/openssl ... But why does the ports system think linux-eagle installs this library? # pkg_info -Lx eagle|grep crypto /compat/linux/lib/libcrypto.so.0.9.8 The file is a symlink and has a distinctively different version number. Regards -- 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: packages compressed with xz
Hello, On 28/11/2010 22:12, Goran Tal wrote: Now that the base system supports xz compression, it should be used as the default compression for packages. Files compressed with xz are smaller and decompress faster than those compressed with bzip2. This can make an installation much quicker, especially when the complete system is installed or upgraded. Any reasons against it? I think it's already in CURRENT. On my notebook xz compression and decompression are much slower than any of the other algorithms supported by tar. It has the best compression ratio, though. ___ 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: /pub or not /pub
On 08/11/2010 22:39, Torfinn Ingolfsen wrote: On Wed, Nov 3, 2010 at 3:20 PM, Dominic Fandrey kamik...@bsdforen.dewrote: It has come to my attention that a lot of FTP mirrors have their FreeBSD data under /FreeBSD instead of /pub/FreeBSD. Which version is recommended and used to create PACKAGESITE from PACKAGEROOT? IMHO, if a site claim to be a mirror, they should follow the structure of the original site. For FreeBSD ftp mirrors, that means /pub/FreeBSD etc. If they provide a /FreeBSD that one should be a link to /pub/FreeBSD and so on. Thanks a lot for this input! I think ~half the German mirrors offer /FreeBSD instead of /pub/FreeBSD, which really messes up my code that generates PACKAGESITE_MIRRORS from PACKAGEROOT_MIRRORS for pkg_upgrade. This is of course not limited to German mirrors. At one point I actually thought there was an official policy change involved and I started changing my code, until I recognized that there are still mirrors around that use the /pub/FreeBSD layout. It would be simple to insert layout probing code, but it would result in an annoying delay for every single call of the program. Especially in small use cases, when it's completely irrelevant that a couple of mirrors don't work. Regards, Dominic -- 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
/pub or not /pub
It has come to my attention that a lot of FTP mirrors have their FreeBSD data under /FreeBSD instead of /pub/FreeBSD. Which version is recommended and used to create PACKAGESITE from PACKAGEROOT? Regards -- 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: Use of license in ports Makefile
On 28/10/2010 00:52, Carmel wrote: I have a application that I want to port to FreeBSD. It is licensed under the BSD license from what I can understand. In the new port's Makefile, would I just put something like this: ... To my understanding this LICENSE stuff is not mature. And the more people use it the more difficult it will become to make changes to it. I won't start using it until it shows up in the Porters' Handbook. -- 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
looking for a committer
I'm looking for a committer for the openarena port: http://www.freebsd.org/cgi/query-pr.cgi?pr=146818 The PR sits there since May. I'd like to work on the ioquake3, ioquake3-devel and iourbanterror ports. The pending openarena commit is blocking, because of changes to the ioquake3 master port. The iourbanterror project currently doesn't have an official engine, there are only some very scary semi-official patchsets on their forums - hence I intend to migrate it to recent ioq3 code. I also have been sent patches to add desktop icons for ioq3, it seems reasonable to add the feature to all the io* ports. After a commit of oa, I also want to work on support for modding tools and update to the latest upstream code, because the project graciously accepted my Makefile patches for FreeBSD. Regards -- 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: looking for a committer
On 13/10/2010 16:52, Warren Block wrote: On Wed, 13 Oct 2010, Dominic Fandrey wrote: I'm looking for a committer for the openarena port: http://www.freebsd.org/cgi/query-pr.cgi?pr=146818 The PR sits there since May. FWIW, I've tested this port successfully. The multiple patches and files in the PR made it confusing to get to the final port, but once there it works fine. Yep, sorry about this. It's difficult to avoid it when the PR sits there for such a long time. One of the shars needed ~3 hours to arrive in the PR, till then I had already resubmitted it, only making that worse. Regards ___ 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: OPTIONS
On 03/10/2010 11:45, David DEMELIER wrote: 2010/10/3 Matthew Seaman m.sea...@infracaninophile.co.uk: I don't want something complex, checkbox, textbox, radiobuttons is enough. Textbox is _very_ complex. Think of all the code you'd have to add to ports to check what was entered by the user. At the very least you have to verify that whatever was provided is valid. For the feature not to become annoying you'd have to be a lot more fuzzy and complex, though. -- 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: OPTIONS
On 03/10/2010 12:29, David DEMELIER wrote: 2010/10/3 Dominic Fandrey kamik...@bsdforen.de: On 03/10/2010 11:45, David DEMELIER wrote: 2010/10/3 Matthew Seaman m.sea...@infracaninophile.co.uk: I don't want something complex, checkbox, textbox, radiobuttons is enough. Textbox is _very_ complex. Think of all the code you'd have to add to ports to check what was entered by the user. At the very least you have to verify that whatever was provided is valid. For the feature not to become annoying you'd have to be a lot more fuzzy and complex, though. What do you mean by valid? In the way that the user can't insert any no alpha-numeric characters or an entry that is only valid to the application ? Text fields are arbitrary and you'd probably want to limit it to a specific purpose, like a list of languages. So is de_* an acceptable language? Do you delimit with space, pipe or semicolon? Do people really want to be bothered with learning the specific syntax of your ports text input fields? -- 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: OPTIONS
On 03/10/2010 12:48, David DEMELIER wrote: 2010/10/3 Dominic Fandrey kamik...@bsdforen.de: On 03/10/2010 12:29, David DEMELIER wrote: 2010/10/3 Dominic Fandrey kamik...@bsdforen.de: On 03/10/2010 11:45, David DEMELIER wrote: 2010/10/3 Matthew Seaman m.sea...@infracaninophile.co.uk: I don't want something complex, checkbox, textbox, radiobuttons is enough. Textbox is _very_ complex. Think of all the code you'd have to add to ports to check what was entered by the user. At the very least you have to verify that whatever was provided is valid. For the feature not to become annoying you'd have to be a lot more fuzzy and complex, though. What do you mean by valid? In the way that the user can't insert any no alpha-numeric characters or an entry that is only valid to the application ? Text fields are arbitrary and you'd probably want to limit it to a specific purpose, like a list of languages. So is de_* an acceptable language? Do you delimit with space, pipe or semicolon? Do people really want to be bothered with learning the specific syntax of your ports text input fields? In the openoffice ports you have LOCALIZED_LANG knob, I needed to check which kind of delimiters was needed and it's a space, so delimit by space is enough. I have set LOCALIZED_LANG wrongly before. An excellent example, why text input boxes are /very dangerous/. -- 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: OPTIONS
On 03/10/2010 12:54, Miroslav Lachman wrote: Dominic Fandrey wrote: On 03/10/2010 11:45, David DEMELIER wrote: 2010/10/3 Matthew Seamanm.sea...@infracaninophile.co.uk: I don't want something complex, checkbox, textbox, radiobuttons is enough. Textbox is _very_ complex. Think of all the code you'd have to add to ports to check what was entered by the user. At the very least you have to verify that whatever was provided is valid. For the feature not to become annoying you'd have to be a lot more fuzzy and complex, though. You don't need to. It is the same as if user put something wrong in to make.conf, ports.conf or even if somebody do: cd /usr/ports/databases/mysql51-server make WITH_CHARSET=UTF13 WITH_XCHARSET=1 WITH_COLLATION=true No, it's technically the same, but from a usability standpoint this is entirely different. In your examples a user makes an educated and competent change, the user acted on his own behalf. When you pop up a dialogue and ask the user for something you better have a) a good reason, b) good defaults, c) give thorough guidance and explanation and d) offer a way to roll back the changes made. Or you can kiss your users good bye. All of them are invalid and not checked by ports framework, so if somebody implements textbox in to OPTIONS framework, the situation will not be worse! Situation will be better for those users not familiar with WITH_ knobs. You're mistaking a usability issue with a technical one. Jef Raskin's Humane Interface is a good starting point. Regards -- 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: porting: Linux to Freebsd
On 02/10/2010 08:42, Chetan Shukla wrote: Hi, Could someone please outline the steps needed in porting a general application from Linux to FreeBSD. If the thing is not tightly coupled to the kernel, the general compile guide to the software you try to compile will suffice most of the time. Regards ___ 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: Using portmaster with different PYTHON_VERSION
On 01/10/2010 01:04, Doug Barton wrote: On 9/29/2010 1:57 PM, Dmitry Pryanishnikov wrote: Hello! 2010/9/28 Doug Bartondo...@freebsd.org: I would also argue that there is a fundamental assumption in the ports infrastructure that what you're doing here (installing both versions on the same system) is not supported. The ability to make the version of things like python or perl variable is a great feature of the ports infrastructure, but my understanding has always been that this would be a system-wide option, and that installing different versions of the same language on the same system is not supported. What problems (besides no support in portmaster) can arise due to parallel use of Python 2 and Python 3 in the same FreeBSD system? I'm not an expert on python so I'll let someone more knowledgeable comment on that. There may not even be any problems. I'd assume this is a correct assumption. I wouldn't expect any problems. My point was simply that historically the assumption has been that there would only be one version of a given interpreted language (like perl or python, and to some extent php, and others) on a system at a time. Your post eloquently stated the case for why that assumption might no longer be true. If that's the case, then the way we do some things might have to change. I've been thinking whether I could abandon the assumption that there is only one package per origin in pkg_upgrade. I decided against it, because the change would be too fundamental. If the assumption was scrapped, there would no longer be a unique identifier for packages across versions and this would introduce guesswork into every layer of code. There is already tons of guesswork in reading the command line parameters, there are 13 different things that can go wrong with packages specified on the command line. Because they can go wrong in different situations (e.g. regular reinstall request or -o), the code currently produces 19 different kinds of error messages just for specified package names. There are another 38 error messages for redundant and conflicting options/flags. Imagine to introduce this degree of error handling into every layer of a package management tool. As far as I am concerned the correct solution would be to create py- slave ports for every major branch, i.e. py2-* and py3-* ports. This way you could have one python version from every major branch, which I'd expect to suffice for most use cases. An alternative would be to have the py-* packages depend on lang/python and make that depend on more than one version of python. I.e. it should allow to select all desired python versions through the OPTIONS framework. The py-* ports then would have to be changed to install themselves for all available python versions they support (this should be possible with a little Makefile magic and dynamic plists). I expect this approach would also work well with the build systems pointyhat and tinderbox. If the ports tree introduced a new unique identifier that crossed version boundaries, was present in INDEX files, +CONTENTS files and of course could be produced by the Makefile, it would be far less trouble to get rid of the origin 1-1 package relation assumption. It would be a lot of work, because the assumption is so heavily relied on, but it would not be very difficult. Regards, Dominic -- 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: Distributed Version Control for ports(7) ( was: Re: autoconf update )
On 20/09/2010 03:01, Carlos A. M. dos Santos wrote: On Sun, Sep 19, 2010 at 6:34 AM, Ion-Mihai Tetcu ite...@freebsd.org wrote: Insert VCS discussion here Is this just my impression or are we trying to build a bikeshed here? I think we all agree, that the stage is not set for a VCS change. Regards -- 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: autoconf update
On 17/09/2010 00:35, Anonymous wrote: Dominic Fandrey kamik...@bsdforen.de writes: On 16/09/2010 19:17, Dmitry Marakasov wrote: * Dominic Fandrey (kamik...@bsdforen.de) wrote: Just out of curiosity, why a version bump because of a build dependency? I don't think an autoconf update should have an effect on any /running/ software but build systems. And I don't see how rebuilding all the software improves it. This is not a criticism - I just think there is something I don't understand and that worries me. My guess is to uncover *early* build failures that exp-run didn't catch. Example is the breakage of databases/postgresql84-server + WITH_ICU. I second the question. Revision bump seem absolutely unnecessary. There was the sweeping commit reason in another thread. But I don't really think it would have been a sweeping commit if it weren't for the version bump. Did you forget that autoconf262 was removed? I don't get it. I've been really dumb a couple of times lately. Maybe that's it. So if you have the patience, explain it like you would to a dumb person. Regards -- 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: autoconf update
On 17/09/2010 06:41, Doug Barton wrote: On 9/16/2010 6:15 PM, Doug Barton wrote: On 9/16/2010 3:35 PM, Anonymous wrote: Dominic Fandreykamik...@bsdforen.de writes: On 16/09/2010 19:17, Dmitry Marakasov wrote: * Dominic Fandrey (kamik...@bsdforen.de) wrote: Just out of curiosity, why a version bump because of a build dependency? I don't think an autoconf update should have an effect on any /running/ software but build systems. And I don't see how rebuilding all the software improves it. This is not a criticism - I just think there is something I don't understand and that worries me. My guess is to uncover *early* build failures that exp-run didn't catch. We shouldn't use our users to beta-test infrastructure changes. Sorry, I'm not feeling well atm and realize that I didn't write what I was thinking here. What I intended to say was that we _don't_ intentionally use the ports system to force our users to beta test changes. I think it goes without saying that we _shouldn't_ do this, although I think that changes like this are a platinum-coated example of why we need to have -stable and -dev branches for ports. I used to disagree with this, because I thought it would create additional work load. I have come to think more favourably of the idea, because you can make more daring commits on a -dev branch and don't have to quick-fix everything that goes wrong. Also the time between a MFC does not have to be very long. A week should be more than enough time to uncover and solve all problems. So the delay to get updates and fixes on the -stable branch is not very long. Regards -- 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: autoconf update
On 16/09/2010 19:17, Dmitry Marakasov wrote: * Dominic Fandrey (kamik...@bsdforen.de) wrote: Just out of curiosity, why a version bump because of a build dependency? I don't think an autoconf update should have an effect on any /running/ software but build systems. And I don't see how rebuilding all the software improves it. This is not a criticism - I just think there is something I don't understand and that worries me. I second the question. Revision bump seem absolutely unnecessary. There was the sweeping commit reason in another thread. But I don't really think it would have been a sweeping commit if it weren't for the version bump. -- 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
autoconf update
Just out of curiosity, why a version bump because of a build dependency? I don't think an autoconf update should have an effect on any /running/ software but build systems. And I don't see how rebuilding all the software improves it. This is not a criticism - I just think there is something I don't understand and that worries me. Regards -- 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: Option in port depending on another port, how to handle ?
On 12/09/2010 15:23, Eric Masson wrote:
Anonymous swel...@gmail.com writes:
NGINX_UWSGI_MODULE_VERSION!= ${MAKE} -V PORTVERSION -C
${PORTSDIR}/www/uwsgi
Great. Seems I really need to improve my make-fu.
Thanks for your answer.
This kind of thing can become a real performance burden if it
becomes commonly used.
Regards
--
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
