Re: missing ports maintainer patches
On Wed, Jun 13, 2012 at 5:41 PM, Sameer Manek ma...@ghur.net wrote: It appears that f...@freebsd.org is no longer involved with maintaining ports that are assigned to that id. http://www.freebsd.org/cgi/query-pr-summary.cgi?responsible=flz Can someone at least review and commit the patches in ports/168262 and ports/168263 I'm still involved. I'll try to deal with the updates tomorrow, sorry for the delay. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkg_delete and +DEINSTALL
On Sun, Jun 10, 2012 at 8:10 PM, Chris Rees cr...@freebsd.org wrote: On 10 June 2012 19:55, Andriy Gapon a...@freebsd.org wrote: While pkgng is growing momentum I have a small suggestion for outgoing pkg_* tools. It seems that pkg_delete performs something like exec(+DEINSTALL, ...). I think that it would be better to do exec(/bin/sh, +DEINSTALL, ...). Rationale: - no need to set x bit on +DEINSTALL - no need to allow exec on /var/db filesystem The problem is discovered by actually using noexec mount option. I don't think this is a bad idea, so I've copied in flz, the de-facto pkg_install maintainer but don't forget that pkg_install is very close to death! Aye. I've just handed my src commit bit for safekeeping but if you're willing to put in the work, the plan sounds good assuming all scripts have been rewritten in shell (for those that weren't already). -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: [ANNOUNCE]: clang compiling ports, take 2
On Mon, Jul 25, 2011 at 8:06 PM, George Liaskos geo.lias...@gmail.com wrote: Hello! I added some jquery for sorting / searching at the latest clang exp run. http://cybertron.gr/errorlogs/amd64-errorlogs/e.9-exp.20110723205754/index.html I hope you 'll find it useful. The table should be sortable already, just click on the column name. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: Opinions on additional small subversion bsd.svn.mk framework
On Sun, Jul 3, 2011 at 9:49 PM, Olli Hauer oha...@freebsd.org wrote: Hi, I want to hear your opinion on a new subversion helper framework [...] Hey Olli, I think that fixing the loose dependency on subversion is a good thing, the rest I don't agree with. We don't want to help people to create ports that fetch sources from svn directly, and replacing a BUILD_DEPENDS line with a USE_SVN= perl doesn't sound that useful to me. A script that fetches sources, creates a tarball and all that could be a nice addition to Tools/scripts though. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: [ANNOUNCE]: clang compiling ports
On Thu, Jun 30, 2011 at 9:19 AM, b. f. bf1...@googlemail.com wrote: Mark Linimon wrote: On Mon, Jun 20, 2011 at 06:21:26PM -0500, Mark Linimon wrote: A permanent URL to this run is: http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp.20110616185105/ That will stick around even if we use amd64-9-exp for something else. I have updated the errorlog-classifier script and re-run the analysis. Most of the false positives for process failed being actually inability to find C compiler are now flagged as assumes_gcc. The linker_error case has been expanded (again, while these can happen in regular runs, they are much more prevalent in the clang runs.) A few other cases have been tightened up as well. Is there a new link for the new results? Or did you use the link above? I'll start a new run and will report the results in a day or two. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: initializing portmaster's local-packagedir
On Thu, Jun 23, 2011 at 3:09 AM, per...@pluto.rain.com wrote: Starting with a single directory containing a few hundred packages (.tbz files), how would I go about converting it into the sort of repository which portmaster could use as its --local-packagedir? I suppose the first step would be something along the lines of mkdir .all mv *.tbz .all mv .all All but how do I figure out which packages go in each of the category directories and in Latest? Categories are listed in INDEX. The name in Latest is called LATEST_LINK in the port itself, but AFAIK it's not recorded anywhere else. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: [ANNOUNCE]: clang compiling ports
On Tue, Jun 21, 2011 at 8:41 AM, Alexander Leidinger alexan...@leidinger.net wrote: Quoting Mark Linimon lini...@lonesome.com (from Mon, 20 Jun 2011 18:21:26 -0500): On Mon, Jun 20, 2011 at 05:37:53PM +0200, Roman Divacky wrote: Flz@ just ran an exp-build with CC=clang and CXX=clang++. The results can be seen here: http://pointyhat.freebsd.org/errorlogs/amd64-9-exp-latest/ A permanent URL to this run is: http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp.20110616185105/ That will stick around even if we use amd64-9-exp for something else. It may be beneficial for such kind of exp runs to have a list which is sorted by number of affected ports. Fixed now. Florent ___ 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: vim python as scripting language
On Sat, May 28, 2011 at 9:24 AM, Gour-Gadadhara Dasa g...@atmarama.net wrote: Hello, I'm moving back from Emacs to Vim, but see that there is no Python enabled since: echo has(python) gives 0, although I see there is the following snippet in Makefile: .if defined(WITH_PYTHON) USE_PYTHON= yes MAKE_ARGS+= CONF_OPT_PYTHON=--enable-pythoninterp .endif Can anyone explain me what is the situation in regard to the vim port Python? (I'm interested to be able to use Python as scripting language, syntax high. works.) You can rebuild the port with WITH_PYTHON=yes. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: vim python as scripting language
On Sat, May 28, 2011 at 12:22 PM, RW rwmailli...@googlemail.com wrote:
On Sat, 28 May 2011 13:00:41 +0200
Gour-Gadadhara Dasa g...@atmarama.net wrote:
On Sat, 28 May 2011 11:23:32 +0100
Florent Thoumie f...@xbsd.org wrote:
You can rebuild the port with WITH_PYTHON=yes.
Thank you.
How is it that there is no 'make config' menu to choose options from?
IIRC the maintainer objects to FreeBSD's option menus. IIWY I'd add it
in make.conf:
.if ${.CURDIR:M*/editors/vim}
WITH_PYTHON=yes
.endif
There's a WITH_VIM_OPTIONS option, but if you select PYTHON it won't
actually work, because the port checks for WITH_PYTHON before
bsd.port.pre.mk is included. So your suggestion is the best bet for
now.
--
Florent Thoumie
f...@freebsd.org
FreeBSD Committer
___
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: net-p2p/rtorrent ui does not come
On Wed, May 25, 2011 at 8:55 AM, Sergey V. Dyatko sergey.dya...@gmail.com wrote: On Tue, 24 May 2011 13:13:51 +0100 Florent Thoumie f...@freebsd.org wrote: This is committed now. I've updated net-p2p/libtorrent-devel and net-p2p/rtorrent-devel as opposed to the non-devel ports as it is considered unstable. you forget remove BROKEN string (see Revision 1.34 by pav@) Fixed now, didn't notice tinderbox was trying to build BROKEN ports. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: net-p2p/rtorrent ui does not come
On Sat, May 14, 2011 at 1:16 PM, Sergey V. Dyatko sergey.dya...@gmail.com wrote: On Sat, 14 May 2011 13:34:23 +0200 Christer Solskogen christer.solsko...@gmail.com wrote: 2011/5/14 Sergey V. Dyatko sergey.dya...@gmail.com: http://tiger.ipfw.ru/files/rtorrent.diff.txt http://tiger.ipfw.ru/files/libtorrent.diff.txt Thanks! It works now on 8.2-RELEASE as well. Just one thing I think you forgot: files/patch-src__display__canvas.h did not apply cleanly. I just deleted that. ooops, yes. That patch useless and must be removed. This is committed now. I've updated net-p2p/libtorrent-devel and net-p2p/rtorrent-devel as opposed to the non-devel ports as it is considered unstable. I haven't been able to reproduce the issue with 0.8.8/0.12.8. I reckon it had to do with the kqueue backend. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: Clean up old PRs
On Mon, May 16, 2011 at 1:02 PM, Jerry je...@seibercom.net wrote: I am proposing a new one: x - expired This report is over 2 years old. If no one has bothered to fix it by now, then in all probability no one will. Not gonna happen, for reasons that have been mentioned previously. If you feel a PR is OBE, then just follow-up to tell us why and we'll close it if we agree. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: net-p2p/rtorrent ui does not come
On Mon, Apr 18, 2011 at 5:42 PM, David Demelier demelier.da...@gmail.com wrote: On 18/04/2011 12:11, Sergey V. Dyatko wrote: On Sun, 17 Apr 2011 10:45:31 +0200 David Demelierdemelier.da...@gmail.com wrote: Hello, Hi, CC`d maintainer I installed net-p2p/rtorrent and the user interface does not come, nothing happens and the rtorrent process raise to 100% use of CPU. I have same issue on recent HEAD, i386. After rebuild rtorrent without xmlrpc-c support it runs fine, but when I quit it hungs. I can provide output of ktrace+kdump output if it necessary. It full of stars^W 96806 initial thread CALL nanosleep(0xbfbfe2c8,0) 96806 initial thread RET nanosleep 0 I can't say exactly when it started, but it looks like long standing issue There is a patch working here for me : http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/155318 Sorry it took me a while, but I've finally committed this patch. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkg_info -g not working for unprivileged user + unreadable files
On Mon, Feb 7, 2011 at 7:52 AM, Doug Barton do...@freebsd.org wrote: flz, In r206043 you converted fexists() in src/lib/libpkg/file.c to use open() instead of lstat(). Unfortunately this has the side effect of breaking 'pkg_info -g' for unprivileged users with files that have no +r bits. For example: pkg_info -g sudo-1.7.4.6 Information for sudo-1.7.4.6: Mismatched Checksums: pkg_info: /usr/local/bin/sudo doesn't exist pkg_info: /usr/local/bin/sudoedit doesn't exist pkg_info: /usr/local/bin/sudoreplay doesn't exist pkg_info: /usr/local/sbin/visudo doesn't exist How can you compute the checksum if you don't have read access? I understand that the error message should rather be Cannot open %s. Reverting your change produces the expected behavior. So my questions are, why was the change made, what are its benefits, and how can we fix this problem? :) I'm sure there was a good reason at the time. I'll have a better look later. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: Users needed or not by ports
On Mon, Oct 11, 2010 at 5:01 PM, David DEMELIER demelier.da...@gmail.com wrote: Hello, Before writing a patch for the ports framework, I just want to be sure that FreeBSD ports shouldn't use a same user added by ports. For example pulseaudio adds some users to the system (pulse, pulse-whatever) and should these users be needed from others ports ? My plan is : 1. Register users added and needed by ports in files like +USERS +GROUPS, 2. When make deinstall or pkg_delete port_name check if the user is still needed by other port (if this is possible) 3. Print a message like The following users and group are not needed anymore by the system : xxx yyy pkgsrc already use something like this, so a port should be really easy to be done. This has already been discussed (including in a thread that you started [1]). This needs support in both ports and pkg_install. [1] http://www.mail-archive.com/freebsd-ports@freebsd.org/msg27486.html -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: Users and groups kept after a port deinstallation
On Fri, May 21, 2010 at 11:11 AM, David DEMELIER demelier.da...@gmail.com wrote: Hi, I used pkgsrc for a while on NetBSD. I was used to the pkgsrc notifications about the users and groups leaves, when some ports are removed these leaves are not used anymore. e.g pulseaudio needs some users on the system. Then the pkgsrc framework says to the user that are some users not used anymore and they could remove them safely. Ports has the lack of this kind of notification, that's why I would start writing a patch in the ports infrastructure, or maybe someone already proposed something else ? I apologize for my bad english. This was discussed in the following bug-report: http://www.freebsd.org/cgi/query-pr.cgi?pr=108514 I think the proper solution is to create a +UGIDS file to be able to maintain a refcount, but the status quo isn't that bad. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: Who will take two patches of www/moinmoin?
On Wed, Apr 28, 2010 at 10:58 AM, khsing khsing...@gmail.com wrote: Recently, I was promoted be a maintainer of moinmoin. I processed two PRs of moinmoin, but who will take these? http://www.FreeBSD.org/cgi/query-pr.cgi?pr=145690 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=145646 Hi, I've just committed the two patches. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: [RFC] deprecate @exec and @unexec in plists in favor of pre-install and post-install scripts
On Wed, Mar 31, 2010 at 11:49 AM, Alexander Leidinger alexan...@leidinger.net wrote: Quoting Florent Thoumie f...@xbsd.org (from Mon, 29 Mar 2010 09:10:54 +): I mentioned getting rid of those pesky @*exec lines a few years ago, but this was met by quite a lot of objection. I still think it would be a good change, assuming that we provide equivalent (or better) features: - Configuration files should be marked and automatically dealt with by the infrastructure, not by esoteric commands. - Subroutines for shell scripts should be provided along with pkg_install, or be installed by a third party port (users/groups creation comes to mind). - Scripts should be automatically picked up as you mentioned. We're trying to shove most targets in pkg-install, but it probably would be best to split it (preinstall, postinstall, predeinstall, postdeinstall). Good thing is, this doesn't require any change in pkg_install since it's already supported. One of the added bonus is that some code that appears both in Makefile and pkg-plist will only be in preinstall/postinstall scripts. Given that a lot of the @(un)exec is comming from ports/Mk/bsd.*.mk, and that you can detect if there is already a pre-/post-install script in bsd.port.mk, it should be not so hard for the people which propose those (IMO good) ideas to come up with a patch for bsd.port.mk which generates pre-/post-install scripts with appropriate commands and does not add the @(un)exec to pkg-plist for those ports, which do not have a pre-/post-install script. That would be a good start indeed, but this is the easy part. It could serve as a proof of concept and would show more clearly what you have in mind. Done nicely, it also allows to keep a lot of the stuff in the Makefile and only write such scripts by hand if absolutely necessary (think about e.g. CREATE_USER=name1:UID1 name2:UID2 which would already cover a lot if not most use cases). CREATE_USER? Have you been living under a rock recently? :-) I suppose Garrett sent this email to get a feel of what the general consensus was. If it turns out that people agree we should get rid of those lines, then I'm sure we can find people willing to do the necessary work. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: [RFC] deprecate @exec and @unexec in plists in favor of pre-install and post-install scripts
On Mon, Mar 29, 2010 at 7:58 AM, Matthias Andree matthias.and...@gmx.de wrote:
Am 28.03.2010, 08:14 Uhr, schrieb Garrett Cooper:
Hi,
As part of taking a look at the differences in our implementation
of pkg_install(1) in order to afford an improvement over the existing
code, I've looked at various implementations of pkg_install, one being
NetBSD's evolution [1]. It's several years ahead from our's and while
I don't believe that all of the complexity is desired, there's a lot
of good lessons to be learned from this. One of which is that they
replaced the @exec and @unexec calls with string pre-install //
post-install and pre-deinstall // post-deinstall scripts. I think that
this potentially is a good step forward because it takes some of the
guts out of the +CONTENTS files and places it in [bourne shell]
scripts, which are easier to maintain and potentially understand.
I realize that some of the loss would be that one couldn't simply
specify things like %f, %D, %F, etc with @exec and @unexec, but that
seems a small price to pay for tuning everything a bit more. On the
plus side too, that means that one could use an extensive set of
shell, etc libraries that would avoid code duplication like what's
present in the +CONTENTS files. This is one of the small observations
I made after starting on work which would modify 1k python ports to
not install the byte-compiled or optimized files (side topic that we
can talk about in another thread if desired).
Thoughts?
Hi Garrett,
I'm not so sure what the advantage would be. For trivial
pre-post-(de)install tasks, why use a separate script? It's less concise
than reading everything in pkg-plist.
WRT variables, I'm not so concerned about %D %F etc, but I am concerned
about the necessity to add script boilerplate (such as snatching pre-post or
deinstall-install modes, prefix), and while I haven't thoroughly audited the
install scripts in ports, I see lots of bad shell scripts around. These
would need rigorous audits (in adverse conditions, such as paths containing
blanks and shell meta characters to unveil underquoted
parameters/variables).
Also, this effort alone isn't any help in reducing code duplication, as in
my perception the duplication is between Makefile (for port install) and
pkg-plist/pkg-install (for packages). There often is some line similar to
${SETENV} PKG_PREFIX=${PREFIX} ${SH} ${PKGINSTALL} ${PKGNAME}
POST-INSTALL
in the ports' Makefiles (post-install or whereever appropriate).
Also, this would need excellent documentation. RPM on Linux is similarly
flexible, but is severely underdocumented (at least RPM v3 and v4 on
openSUSE Linux are). If it does any _undocumented_ magic, I don't want it.
:)
So, before we think about it and harrass hundreds of ports maintainers, we'd
need the shell script library in place to make it a selling point for
actually using install scripts; at that point we can re-think about moving
stuff out of pkg-plist into pkg-install scripts. At the *same* time (so that
only one edit cycle is needed for affected ports - and I'd suggest a survey
to see how many, hundreds probably), we should consider making
Mk/bsd.port.mk call the install scripts automatically (needs changes to
hundreds of ports again) in pre-install, post-install and related stages.
I mentioned getting rid of those pesky @*exec lines a few years ago,
but this was met by quite a lot of objection.
I still think it would be a good change, assuming that we provide
equivalent (or better) features:
- Configuration files should be marked and automatically dealt with by
the infrastructure, not by esoteric commands.
- Subroutines for shell scripts should be provided along with
pkg_install, or be installed by a third party port (users/groups
creation comes to mind).
- Scripts should be automatically picked up as you mentioned. We're
trying to shove most targets in pkg-install, but it probably would be
best to split it (preinstall, postinstall, predeinstall,
postdeinstall). Good thing is, this doesn't require any change in
pkg_install since it's already supported.
One of the added bonus is that some code that appears both in Makefile
and pkg-plist will only be in preinstall/postinstall scripts.
--
Florent Thoumie
f...@freebsd.org
FreeBSD Committer
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Best way to have a port...
On Tue, Mar 2, 2010 at 6:51 AM, M. Warner Losh i...@bsdimp.com wrote:
... that builds part of FreeBSD?
Let me back up...
I'm trying to create a port for gcc and binutils that is configured
for FreeBSD for a given machine. FreeBSD mips, say. binutils was
relatively easy (once I ported our mips support forward). However,
gcc vexes me. It requires, to build libgcc and friends, a fully
populated include tree. And it wants to use
/usr/local/freebsd-mips/include instead of /usr/include (which is
good). However, the former doesn't exist. I'd like to create a port
for it, but I'm unclear how to even start. This port should consist
of all files from make includes TARGET_ARCH=mips.
So, some questions: First, how do I know where the FreeBSD source tree
is? Is there some standard define like SYSDIR that contains this
infomration?
Second, I need to invoke make includes (and a few other things), with
some slightly non-standard args. is there a stylied way to do this?
I'd like to avoid extracting everything into myport/work/FreeBSD :)
Without solving these problems, the notion that we can use a ports
compiler to build FreeBSD becomes less viable...
IIUC, you really want one new port that installs all mips headers. The
gcc/binutils port can be modified for ${ARCH} == mips.
Something like this should work:
http://people.freebsd.org/~flz/local/ports/freebsd-mips.shar
The thing is, it will have to be modified everytime a header is
added/removed. The easy way out is to only support HEAD so you don't
have to use OSVERSION conditionals. The other solution I'm seeing is
to fetch sources from FTP (which is obviously more work).
--
Florent Thoumie
f...@freebsd.org
FreeBSD Committer
___
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: UIDs question
On Wed, Jan 6, 2010 at 8:26 PM, Jason jhelf...@e-e.com wrote:
Hi,
I am new to building ports, however I have started to get the hang of
things.
I am not building any ports that I intend on submitting to FreeBSD, yet,
however maybe that isn't too far off :)
I've used a guide I found to create a local ports repository that is working
out wonderfully with the existing ports tree under /usr/ports
My tree is under /usr/ports/local, and I found a way to integrate a local
UIDs and GIDs file, by setting this variable in my Makefile:
UID_FILES:=${PORTSDIR}/local/UIDs
When I go to install my port it installs the user as expected, however it
fails on the ${INSTALL_PROGRAM} function. I understand this is just using
install with the appropriate flags. Obviously, the port doesn't install.
If I run it again, the user is already on the system, and the port installs
successfully.
I was wondering if there is a way to have the port install the user using
the native USERS or GROUPS directives in the do-install phase with the
INSTALL macros, or if there is a more suggested, or conventional, way of
doing this operation.
Would you mind putting the files somewhere and showing us the error
log? I am aware of one caveat at the moment, which is that you can't
use users/groups created with USERS/GROUPS in pkg-plist. Every typical
use case with directives contained in Makefile should be fine AFAIK.
--
Florent Thoumie
f...@freebsd.org
FreeBSD Committer
___
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 the fakeroot patch
On Mon, Dec 14, 2009 at 3:13 PM, Baptiste Daroussin
baptiste.darous...@gmail.com wrote:
Hi all,
I have updated the fakeroot patch, it now can apply on an uptodate version of
the ports.
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/133815
For information the fakeroot patch is a port of the midnightbsd's mports
fakeroot
to freebsd's ports.
What it does:
- it is optional: you can activate it globally with USE_FAKE=yes in
/etc/make.conf or per ports by adding USE_FAKE=yes in the ports Makefile
I don't know if this should be a port setting. I think this should be
a user setting. So, I think WITH_FAKE / WITH_FAKEROOT is a better
choice. Obviously ports not working with fakeroot would have to define
something like IGNORE_FAKEROOT, the same kind of variable we have for
MAKE_JOBS.
- it create a fakeroot directory in the WRKDIR where all the binary are
installed first
- then it creates a package using the plist and finding its files only in the
fakeroot directory
- in the end it installs the created packages
- it respects the DESTDIR implementation (it is not the same kind of feature
nor
the same goal)
- it does not require any modification on actual ports (except for those which
are already not clean) but will allow to cleanup some ports if wanted.
Why this patch:
- it prevents installing crufts thing on users systems (only what is found in
the plist is really installed, so the package is always clean)
I now that porters should take care of not breaking the plist, but it often
happens, helping them by a system that completly use the plist file is IMHO a
better thing, and it prevents users from being inpacted by a lazy porter.
- it allow to create tinderbox that does not need to install a ports to get
the
package build, only build-depends ports will be installed
- it allow easier handling of NOPORTDOCS, NOPORTEXAMPLES and so on, because it
creates the packages first using plist to know which files should be
packaged,
the porter should only take care of one case, the case everything is
installed, then he adapts the plists to have or not some files depending on
the options the user have.
This should cleanup a lot some ports, and should easier the respectness of
some porting guidelines
What could be done:
because it generates packages first we could imagine some lint programs that
analyse the package content to test that it respects some of the freebsd
recommandation for packages (usefull for porters), it could help the
validation
of new/update ports submission and help preventting commiting buggy stuff.
I'm thinking files could be moved from the fakeroot directory instead
of copied, that way you could run 'find ${FAKEDIR} ! -type d' and find
out if you've missed anything.
Limitation:
this path (currently activable on depend) add from disk usage than the way
ports
actually works:
without the patch:
build - copy on the filesystem
with the path:
build - copy-on-fakeroot-package_building-package-installing
In the future it could be improved by provinding a version of pkg_create that
fake the package creation by directly install on FS so that could become
build-copy-on-fakeroot-package-installing
On pointyhat, a package will be generated at the end regardless. Also,
quite a lot of tools do make a package backup before deinstalling, so
I don't see this as a major issue. If people don't like the I/O
overhead, we could use pkg_add in slave mode, it will skip the package
building phase.
This patch is not yet complete, it should work with classical ports that use
gmake or make and with python, I have only done that currenly as a proof of
concept.
Tell me if you think that this patch could be interesting or not
As I mentioned it before, I think it's a very valuable feature to have.
--
Florent Thoumie
f...@freebsd.org
FreeBSD Committer
___
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
Fwd: cvs commit: ports/Mk bsd.port.mk ports/audio/pulseaudio Makefile pkg-install ports/devel/dbus Makefile pkg-install ports/sysutils/hal Makefile ports/sysutils/hal/files pkg-install.in ports/sysu
FYI. Use as follows: USERS= foo GROUPS= foo ... where foo is the user/group from UIDs and GIDs. Simplez! -- Forwarded message -- From: Florent Thoumie f...@freebsd.org Date: Sun, Sep 6, 2009 at 10:18 PM Subject: cvs commit: ports/Mk bsd.port.mk ports/audio/pulseaudio Makefile pkg-install ports/devel/dbus Makefile pkg-install ports/sysutils/hal Makefile ports/sysutils/hal/files pkg-install.in ports/sysutils/policykit Makefile pkg-install ... To: ports-committ...@freebsd.org, cvs-po...@freebsd.org, cvs-...@freebsd.org flz 2009-09-06 21:18:50 UTC FreeBSD ports repository Modified files: Mk bsd.port.mk audio/pulseaudio Makefile devel/dbus Makefile pkg-install sysutils/hal Makefile sysutils/hal/files pkg-install.in sysutils/policykit Makefile pkg-install x11/gdm Makefile pkg-install Removed files: audio/pulseaudio pkg-install Log: Add support to create users and groups from information stored in UIDs/GIDs files. Users and groups won't be deleted at deinstall time as we're lacking a refcount to know if any port is using them. Also convert a few ports while I'm here. PR: ports/108514 Submitted by: mm, self Revision ChangesPath 1.627 +89 -3 ports/Mk/bsd.port.mk 1.48 +4 -4 ports/audio/pulseaudio/Makefile 1.6 +0 -63 ports/audio/pulseaudio/pkg-install (dead) 1.76 +4 -1 ports/devel/dbus/Makefile 1.6 +0 -27 ports/devel/dbus/pkg-install 1.58 +4 -1 ports/sysutils/hal/Makefile 1.5 +0 -27 ports/sysutils/hal/files/pkg-install.in 1.20 +4 -1 ports/sysutils/policykit/Makefile 1.6 +0 -27 ports/sysutils/policykit/pkg-install 1.124 +4 -1 ports/x11/gdm/Makefile 1.15 +0 -30 ports/x11/gdm/pkg-install -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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 does py25 mean?
On Tue, Aug 4, 2009 at 9:48 PM, Lars Eighnerportsu...@larseighner.com wrote: What does py25 mean? I can't seem to upgrade about 40 ports (the old versions of which now seem to be broken) evidently because the build of py25-gtk-2.13.1 fails with the message py25-cairo-1.8.6 needs Python 2.6 at least. But you specified 2.5. Well, of *I* did not specify 2.5. But howcome something called py25-cairo needs Python 2.6? What does that py25 on the front mean? Doesn't it mean python 2.5? If it doesn't mean that, what does it mean? If it does mean that, then howcome it needs python 2.6? Looking at graphics/py-cairo history: June 17: was updated to 1.8.4 June 19: required python 2.6+ You most likely installed it before that, and probably before python 2.6 was set as the default version. The message is a bit misleading but as somebody else said, the py25- prefix in that case comes from your installed version of python. Check entry 20090608 about the python upgrade in /usr/ports/UPDATING. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkg_info: package files checked before installed packages
On Fri, Jan 16, 2009 at 5:38 PM, Andriy Gapona...@icyb.net.ua wrote: on 16/01/2009 14:52 Andriy Gapon said the following: [people who touched pkg_info recently are CC-ed] Please see a prior discussion here: http://docs.freebsd.org/cgi/mid.cgi?496F360E.1000508 and especially this post: http://docs.freebsd.org/cgi/mid.cgi?7d6fde3d0901152330p32c51b64i212c660c0aaeb04c So it is obvious from code in usr.sbin/pkg_install/info/perform.c, function pkg_do() that if for a given name there is both a package file in a defined packages directory and also an installed package, then pkg_info would work on the package file. Additional info - this issue manifests itself if PKG_PATH env var points to a directory with (full of) packages. Apparently portupgrade sets it so (maybe -p option is needed for that). I do not think that this is either obvious/intuitive or even correct. At the very list there should be an option to control this behavior. I have a system where I keep package files for all installed/built packages and pkg_info acts very nasty there, especially when working on all packages. Is there a patch addressing this issue? -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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 Songbird (how to make a Linux port)
On Fri, Jun 5, 2009 at 5:40 PM, Eitan Adlereitanadlerl...@gmail.com wrote: Martin Wilke wrote: On Thu, Jun 04, 2009 at 06:51:56PM -0400, Eitan Adler wrote: Here is the start of a Makefile for Songbird http://isis.poly.edu/~eitan/files/Songbird-Makefile-v1 The porter's handbook doesn't have a section on the Linux ports (as far as I could tell). I also don't know how I could just mv the files that have to be moved. There is no compiling involved - just running the program. Gecko Team is working on a nativ port :-) True - but we also have linux versions of Firefox and Thunderbird ;) Plus we still should have some documentation on making a linux-* port. The only reason for that is to be able to use linux plugins AFAIK. I'm not aware of any binary-only linux plugin for songbird. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: make.conf no x option
On Tue, May 26, 2009 at 12:37 PM, Peter Pentchev r...@ringlet.net wrote: On Tue, May 26, 2009 at 08:32:50PM +0900, Randy Bush wrote: as so many folk build server-only, there must e a make.conf or whatever option to tell ports that you just do not want an x server or any of it's 500kg friends. but i can not seem to find it. i do cvsup-without-gui, emacs-nox11, etc. but one mistake with some port, and you get the whole boatload, and you can never scrape it all out. I think you're looking for WITHOUT_X11=yes :) I would add WITHOUT_GUI as well, just in case. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [headsup] call for assistance with ports broken on -current
On Mon, Mar 2, 2009 at 9:34 AM, Eygene Ryabinkin rea-f...@codelabs.ru wrote: Mark, good day. Sun, Mar 01, 2009 at 06:45:39PM -0600, Mark Linimon wrote: With 8.0 coming up, it's time to take a look at the ports that have been broken by some recent changes to freebsd-current. I have put a list of these ports, categorized by which change, on the wiki at http://wiki.freebsd.org/PortsBrokenOnCurrent. Could you or someone else add ports/129881 as the ARPv2 changes resolution fix for the ospfd? I am not eligible to edit the wiki pages, so can't do it for myself. Isn't this PR ready for commit already? It seems that the only thing blocking it is maintainer approval, but we're well beyond that now. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [headsup] call for assistance with ports broken on -current
2009/3/2 Eygene Ryabinkin rea-f...@codelabs.ru: Florent, good day. Mon, Mar 02, 2009 at 11:03:38AM +, Florent Thoumie wrote: On Mon, Mar 2, 2009 at 9:34 AM, Eygene Ryabinkin rea-f...@codelabs.ru wrote: Could you or someone else add ports/129881 as the ARPv2 changes resolution fix for the ospfd? I am not eligible to edit the wiki pages, so can't do it for myself. Isn't this PR ready for commit already? It seems that the only thing blocking it is maintainer approval, but we're well beyond that now. Precisely. If someone will take the powers and commit the patches from PR, I will be very grateful. Ok I'll take care of it. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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
Fwd: OpenBGPd Package - recent patch
I received the following email yesterday but I'm not maintaining the port anymore. Furthermore, I think that farrokhi@ has been MIA for a while now (CC'ed anyway). Is there anybody interested in (helping) maintaining net/openbgpd (and possibly net/openospfd)? If so, please contact Franz with patches (and eventually send-pr). TIA -- Forwarded message -- From: Franz Bettag [ QS Housing ] fbet...@qs-housing.net Date: Tue, Feb 24, 2009 at 5:44 PM Subject: OpenBGPd Package - recent patch To: f...@freebsd.org Dear Florent, i was wondering when this patch will be applied: http://kerneltrap.org/mailarchive/openbsd-misc/2008/12/10/4389284 This bugfix is quite important and seems to be commited to the current version of openbgpd. Since i am not that good at coding C, my question would be when you could apply this patch/bugfix in general so i can make my openbgpd servers more secure. Compiling a recent version of openbgpd (4.4, 4.4.1) with the patches from net/openbgpd/files/patch-* seems to not work properly ;) Hope to hear from you soon! Mit freundlichen Grüßen / best regards Franz Bettag -- QS Housing - Technische Leitung Ludwigstrasse 45-47 90402 Nürnberg Fon +49 (0)911 21757 0 Fax +49 (0)911 21757 1 http://www.qs-housing.net -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Question about WRKSRC
On Thu, Feb 5, 2009 at 5:20 PM, Paul Schmehl pschmehl_li...@tx.rr.com wrote:
-Original Message-
From: owner-freebsd-po...@freebsd.org
[mailto:owner-freebsd-po...@freebsd.org] On Behalf Of Florent Thoumie
Sent: Wednesday, February 04, 2009 3:49 AM
To: Schmehl, Paul L
Cc: freebsd-ports@freebsd.org
Subject: Re: Question about WRKSRC
On Wed, Feb 4, 2009 at 4:42 AM, Paul Schmehl pa...@utdallas.edu wrote:
I maintain the sguil ports; security/sguil-server, security/sguil-sensor
and
security/sguil-agent. It came to my attention today that the pkg-install
script that I've written for the security/sguil-server port fails during
package building. (The script works fine when compiling from source.)
The problem appears to be related to the location of WRCSRC, which appears
to be different than it is when building from source. Am I correct about
that? Is WRCSRC different when building packages? If so, is there a way
to
differentiate programmatically between a port being built from source and
one being built from a package?
There's no WRKSRC directory when a package is installed.
I've had a look at sguil-server and you have two options. The first
one is to install your sql script somewhere under ${DATADIR} then read
it from there in your pkg-install script. The second, better in my
opinion, is to move most of your POST-INSTALL target into a shell
script of its own that you'll install in ${DATADIR} (note that it
still requires to install that sql file as well). Quick look shows
that your port is interactive, and not marked as such in Makefile. If
you choose to go with solution #1, then you'll have to set
IS_INTERACTIVE=yes (unless I'm wrong of course).
I assume, if I go with option 2, that the script would have to be run
manually by the individual installing the port? IOW, it wouldn't launch
automagically at the end of the install?
Right. You can mention it pkg-message for example.
--
Florent Thoumie
f...@freebsd.org
FreeBSD Committer
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Question about WRKSRC
On Wed, Feb 4, 2009 at 4:42 AM, Paul Schmehl pa...@utdallas.edu wrote:
I maintain the sguil ports; security/sguil-server, security/sguil-sensor and
security/sguil-agent. It came to my attention today that the pkg-install
script that I've written for the security/sguil-server port fails during
package building. (The script works fine when compiling from source.)
The problem appears to be related to the location of WRCSRC, which appears
to be different than it is when building from source. Am I correct about
that? Is WRCSRC different when building packages? If so, is there a way to
differentiate programmatically between a port being built from source and
one being built from a package?
There's no WRKSRC directory when a package is installed.
I've had a look at sguil-server and you have two options. The first
one is to install your sql script somewhere under ${DATADIR} then read
it from there in your pkg-install script. The second, better in my
opinion, is to move most of your POST-INSTALL target into a shell
script of its own that you'll install in ${DATADIR} (note that it
still requires to install that sql file as well). Quick look shows
that your port is interactive, and not marked as such in Makefile. If
you choose to go with solution #1, then you'll have to set
IS_INTERACTIVE=yes (unless I'm wrong of course).
--
Florent Thoumie
f...@freebsd.org
FreeBSD Committer
___
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: X drivers depend on Gnome?
On Wed, Feb 4, 2009 at 1:55 PM, Alex Goncharov alex-goncha...@comcast.net wrote: ,--- I/Alex (Wed, 04 Feb 2009 08:11:30 -0500) * | The use of USE_ make file variable should conform to what bsd.port.mk | says, IMHO. | | | pkgconfig could be extracted from the USE_GNOME stuff, and it could | | even maintained by someone else than the FreeBSD gnome team, but the | | FreeBSD gnome team is doing a good job at maintaining it, and | | there's no benefit in extracting pkgconfig from USE_GNOME. | | I am not sure I agree with you -- but why would this matter, right? ,--- You/Florent (Wed, 4 Feb 2009 13:21:15 +) * | Please send patches. Kthxbye. Does this mean that you agree with me in principle and if I send you patches, there is a high probability they will he accepted (provided they work, of course)? Thank you, good bye, In principle yes. Now you do have to understand that this is a lot of boring work and you'll need approval from portmgr@, not just me. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: X drivers depend on Gnome?
On Wed, Feb 4, 2009 at 1:11 PM, Alex Goncharov alex-goncha...@comcast.net wrote: ,--- You/Alexander (Wed, 04 Feb 2009 08:37:40 +0100) * | ,--- You/Jeremy (Tue, 03 Feb 2009 17:19:12 -0600) * | | The pkg-config is not GNOME. Even the GTK+2 is not GNOME. | | I am VERY surpised about that you are whining over it. | | In other words, you think that making base X11 blocks (such as drivers | and libxcb) depend on Gnome, per this definition in bsd.port.mk: | | # USE_GNOME - A list of the Gnome dependencies the port has (e.g., | # glib12, gtk12). Implies that the port needs Gnome. | # Implies inclusion of bsd.gnome.mk. See bsd.gnome.mk | # or http://www.FreeBSD.org/gnome/docs/porting.html | # for more details. | | is the right thing, correct? First off, thanks for your detailed reply and getting to the core of my question (obviously, the size of pkg-config is not an issue.) | To repeat what mezz said, the X stuff does not depend upon | GNOME. The X stuff depends upon pkgconfig. pkgconfig is also used by | GNOME. It's a little and useful infrastructure thing. With pkgconfig | you can check if software Y is installed, which version it has, | which include path you need to compile it, and which libs to link to | if you want to use it in your software Z. All it does is to do echo | $libs or echo $includes or similar. The benefit is that you as a | author of software Y just need a little config file which lists | everything, and pkgconfig is responsible for all the common tasks | like version check and printing. It also unifies the interface if | you need to query for software. To tell you the truth, I know what pkg-config does -- a very useful tool, indeed. | It originated in GNOME, but as it is small and light, it is used now | in more or less everything. For example openssl uses it too (but | unfortunately openssl in the FreeBSD base system does not install | the corresponding config file), but this does not make openssl | depend upon GNOME. A perfect example -- you can see the difference in how X and openssl approach this: -- $ grep -i 'pkgconfig[^/]*$' Mk/bsd.openssl.mk Mk/bsd.port.post.mk Mk/bsd.xorg.mk security/openssl/Makefile x11-drivers/xf86-video-nv/Makefile| less Mk/bsd.xorg.mk:# app - requires pkgconfig, don't install shared libraries (I guess) Mk/bsd.xorg.mk:USE_GNOME+= pkgconfig Mk/bsd.xorg.mk:USE_GNOME+= pkgconfig Mk/bsd.xorg.mk:USE_GNOME+= pkgconfig Mk/bsd.xorg.mk:USE_GNOME+= gnomehack pkgconfig security/openssl/Makefile: -e 's|lib/pkgconfig|libdata/pkgconfig|g' \ -- | It just looks to you like GNOME because the config variable in our | ports infrastructure is spelled USE_GNOME. This is for historical | reasons, it could also be named USE_INFRASTRUCTURE (it | automatically adds suitable BUILD_DEPENDS, RUN_DEPENDS and/or | LIB_DEPENDS and additional stuff just by adding a keyword). And this is my point -- change the make files appropriately. While Gnome is great, many people don't use it and don't want to be confused and be quietly dragged into Gnomedom. The use of USE_ make file variable should conform to what bsd.port.mk says, IMHO. | pkgconfig could be extracted from the USE_GNOME stuff, and it could | even maintained by someone else than the FreeBSD gnome team, but the | FreeBSD gnome team is doing a good job at maintaining it, and | there's no benefit in extracting pkgconfig from USE_GNOME. I am not sure I agree with you -- but why would this matter, right? Please send patches. Kthxbye. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: how to install a port without install: in the Makefile
On Wed, Jan 28, 2009 at 4:56 AM, Dmitry Marakasov amd...@amdmi3.ru wrote: * Florent Thoumie (f...@xbsd.org) wrote: You are lucky guys you have not lived in USSR. otherwise you'd surely like alternative ways :) In soviet russia, alternative ways like you. I wish people remembered KISS more than TIMTOWTDI. PLIST_* seems S enough for me :) Which S are we talking about exactly? :-) -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: GNOME, X11, FORTRAN
On Sun, Jan 25, 2009 at 8:27 PM, Garrett Cooper yanef...@gmail.com wrote: On Jan 25, 2009, at 5:18, Robert Huff roberth...@rcn.com wrote: bf writes: Just a note to those of you who helped to integrate the Gnome, X11, and Fortran updates in Ports: thank you very much for the work that you have put in, and for your efforts to find and solve any remaining problems. Hear, hear. I definitely third that. Thanks guys for all the hard work and beers are on me if you come down to South Bay area :). -Garrett Tell you what, I'll pay for the beer if you get me flights. Deal? :-) -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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 required to rebuild after upgrading Xorg to 7.4
On Fri, Jan 23, 2009 at 10:35 PM, Dominic Fandrey kamik...@bsdforen.de wrote: This is the list of ports that I require to rebuild after the upgrade. This list only contains ports directly linked to an now outdated library. It has been generated with the command: # pkg_libchk -qo pkg_libchk is installed by the port sysutils/bsdadminscripts. graphics/cairo sysutils/ecore-config x11/efreet x11-wm/enlightenment-devel graphics/evince devel/gconf2 graphics/gegl graphics/gimp-app security/gnome-keyring math/gnuplot graphics/graphviz x11-toolkits/gtk20 palm/jpilot x11-toolkits/libbonoboui devel/libnotify graphics/librsvg2 math/octave x11-toolkits/pango net-im/pidgin sysutils/policykit-gnome multimedia/transcode net/wireshark multimedia/vlc Did you run portupgrade -rf libxcb? -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: how to install a port without install: in the Makefile
On Thu, Jan 22, 2009 at 10:05 PM, Dmitry Marakasov amd...@amdmi3.ru wrote: * Florent Thoumie (f...@xbsd.org) wrote: If it's just a single file, the preferred way is to add PLIST_FILES=bin/program_name to the Makefile and not use pkg-plist at all. No, no, no. This is not *preferred*. Is it not? Why? There's no reason to introduce pkg-plist for just a single file. This is just an alternative way of doing it. I, for one, don't like it. Same goes for PLIST_DIRS. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: how to install a port without install: in the Makefile
On Fri, Jan 23, 2009 at 1:22 PM, Max Brazhnikov m...@issp.ac.ru wrote: On Fri, 23 Jan 2009 06:58:02 -0600, Jeremy Messenger wrote: On Fri, 23 Jan 2009 03:47:38 -0600, Florent Thoumie f...@xbsd.org wrote: On Thu, Jan 22, 2009 at 10:05 PM, Dmitry Marakasov amd...@amdmi3.ru wrote: * Florent Thoumie (f...@xbsd.org) wrote: If it's just a single file, the preferred way is to add PLIST_FILES=bin/program_name to the Makefile and not use pkg-plist at all. No, no, no. This is not *preferred*. Is it not? Why? There's no reason to introduce pkg-plist for just a single file. This is just an alternative way of doing it. I, for one, don't like it. Same goes for PLIST_DIRS. +1 You are lucky guys you have not lived in USSR. otherwise you'd surely like alternative ways :) In soviet russia, alternative ways like you. I wish people remembered KISS more than TIMTOWTDI. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: how to install a port without install: in the Makefile
On Fri, Jan 23, 2009 at 3:46 PM, Steve Franks bahamasfra...@gmail.com wrote: I presume Florent's preferred method is INSTALL_PROGRAM? So far, the only doc I've found is that it exists. So I put INSTALL_PROGRAM $(WORKDIR)/$(PORTNAME) (portname just happens to be the name of the executable) in the port Makefile, or what? I've never been able to 'read' makefiles, so I'm not sure a look at ports.mk is going to cause anything but frustration. We've spent minutes arguing philisophy, can I get a couple seconds of example? :) Otherwise, PLIST_FILES looks like it will work to me... It's not about installing files but rather registering them. PLIST_FILES/PLIST_DIRS is just a way to replace pkg-plist, for wrong reasons. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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
Fwd: [review] cvs commit: ports MOVED ports/Mk bsd.gecko.mk bsd.port.mk bsd.xorg.mk ports/astro/boinc-setiathome-enhanced Makefile ports/astro/celestia Makefile ports/astro/openuniverse Makefile po
FYI. Report problems on freebsd-...@. -- Forwarded message -- From: Florent Thoumie f...@freebsd.org Date: Fri, Jan 23, 2009 at 4:30 PM Subject: [review] cvs commit: ports MOVED ports/Mk bsd.gecko.mk bsd.port.mk bsd.xorg.mk ports/astro/boinc-setiathome-enhanced Makefile ports/astro/celestia Makefile ports/astro/openuniverse Makefile ports/astro/xtide Makefile ports/audio/fmit Makefile ... To: f...@freebsd.org flz 2009-01-23 16:28:36 UTC FreeBSD ports repository [...] Log: - Update X.org ports to 7.4+ (few ports are more recent than the katamari). - Bump PORTREVISION for all ports depending on libglut since the shlib version number went from 4 to 3. - Bump PORTREVISION for all ports depending on libXaw as libXaw.so.8 isn't installed anymore. - Couple of ports fixes (mostly missing xorg components added to USE_XORG). -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: how to install a port without install: in the Makefile
On Fri, Jan 23, 2009 at 7:12 PM, Doug Barton do...@freebsd.org wrote: Florent Thoumie wrote: It's not about installing files but rather registering them. PLIST_FILES/PLIST_DIRS is just a way to replace pkg-plist, for wrong reasons. I respectfully disagree my friend. :) There was a time back when disks were a lot smaller that saving inodes was a noble thing. Nowadays (for the most part) that is not really a consideration, but personally I still find it convenient to list as much as possible in the Makefile. It saves cvs churn in any case. Come on, it was 2004, not 1994. Disks were already large and cheap. This only adds complexity which in the end adds more code to bsd.port.mk (which could already do with a good diet) and slows things down (which of course is less and less of an issue, but still worth mentioning). -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: how to install a port without install: in the Makefile
On Thu, Jan 22, 2009 at 5:44 PM, Dmitry Marakasov amd...@amdmi3.ru wrote: * Olivier SMEDTS (oliv...@gid0.org) wrote: and of course you must have bin/program_name in pkg-plist. If it's just a single file, the preferred way is to add PLIST_FILES=bin/program_name to the Makefile and not use pkg-plist at all. No, no, no. This is not *preferred*. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: move x11/xclock to x11-clocks/
On Wed, Jan 21, 2009 at 3:58 PM, Eitan Adler eitanadlerl...@gmail.com wrote: Proposal: move x11/xclock to x11-clocks/xclock Makes sense, please submit a PR and specify that I'll handle the PR when the repocopy is done. Thanks. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: Can someone commit ports/130301 (fix mail/fetchmail MASTER_SITE_SUBDIR)
On Fri, Jan 9, 2009 at 11:01 AM, Matthias Andree matthias.and...@gmx.de wrote: please? I think Pav committed the fix right after you sent the email yesterday. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: Can someone commit ports/130301 (fix mail/fetchmail MASTER_SITE_SUBDIR)
2009/1/9 Pav Lucistnik p...@freebsd.org: Florent Thoumie píše v pá 09. 01. 2009 v 11:13 +: On Fri, Jan 9, 2009 at 11:01 AM, Matthias Andree matthias.and...@gmx.de wrote: please? I think Pav committed the fix right after you sent the email yesterday. I don't think I did :) Well the port fetched fine for me, so I don't see 130301 as that much pressing. I wonder what's the status of Simon, I'd like to give him few more days to answer. Oops, I didn't see the two subjects were different. My mistake. -- Florent Thoumie f...@freebsd.org FreeBSD Committer ___ 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: RFC: $USE_[GU]ID for consistent [GU]ID handling
On Sun, Dec 7, 2008 at 6:32 PM, Hiroki Sato [EMAIL PROTECTED] wrote:
Hello,
I would like your comments about the attached patch. This is for
adding USE_UID and USE_GID which allow uid/gid addition on
installation and the removal on deinstallation. It uses
${PORTSDIR}/[GU]IDs for the detail information and can eliminate
complex shell scripts from individual ports.
For example, if you define
USE_UID= foo
in Makefile, the uid foo is added before pre-su-install, and
removed on deinstallation by using pw(8). If the uid already exists,
no error occurred. The multiple uids are also allowed.
The attached patch includes an example of rewrite of an existing
ports (japanese/sj3-server). After investigating ~300 ports in the
ports tree which add uid/gid I think the attached implementation can
cover most of the use case, but there may be something I missed.
Comments are welcome.
Hi Hiroki-san,
There's an open PR with patches for this feature (ports/108514). Could
you have a look and maybe send your comments?
--
Florent Thoumie
[EMAIL PROTECTED]
FreeBSD Committer
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xorg - minimal
On Sat, Oct 18, 2008 at 4:48 AM, Peter Jeremy [EMAIL PROTECTED]wrote: On 2008-Oct-17 10:32:41 -0400, Eitan Adler [EMAIL PROTECTED] wrote: Here is the list I generated from pkg_info when I was first able to run the X server. If anyone is able to run startx with fewer ports please let me know. You should be able to get by without any gnome baggage. How can I handle the video drivers? Not all systems need all drivers. I don't want to depend on xorg-drivers, however you can't get X to start without a video driver. Can some kind of check be done in the Makefile? Unless you actually install all the drivers, go through the configuration process to work out which ones to use and then uninstall the rest, the best you could probably do is to run pciconf and use a config file to map PCI IDs to potential video drivers. Some things to keep in mind with this approach are: - pciconf has to run as root and so has to be inside the su part. - Some video cards have different potential drivers (eg Intel, nVIDIA). - People may have multiple, different video cards present. - Several drivers are virtual (eg dummy, fbdev) Or you can just depend on xorg-drivers, and let people select the drivers they want if they use ports. They will get 8 of them (instead of the whole bunch) if they use packages, this will be down to 5 once the ports are upgraded to xorg 7.4. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports/125625: [PATCH] dns/nsd: USE_RC_SUBR != yes
On Tue, Jul 22, 2008 at 11:41 PM, Olafur Osvaldsson [EMAIL PROTECTED] wrote: Why has committing a patch gotten so complicated? One day since the last update to the PR... The PR responsible recently got repository privileges so he's probably getting familiar to the procedures. While I'm looking at it, you're checking if NO_INSTALL_MANPAGES which is wrong. This variable is meant to be set by ports, not users. Even if it were, you would end up with a incomplete packing list, because your port installs manual pages unconditionally. I'd suggest getting rid of the check completely. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports/125625: [PATCH] dns/nsd: USE_RC_SUBR != yes
On Wed, Jul 23, 2008 at 12:30 PM, Olafur Osvaldsson [EMAIL PROTECTED] wrote: This is something the PR responsible introduced in his original patch... It's still present in your version. Anyway, I'm not blaming anyone, just pointing out what I think is a mistake. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports/125625: [PATCH] dns/nsd: USE_RC_SUBR != yes
On Wed, Jul 23, 2008 at 1:12 PM, Ion-Mihai Tetcu [EMAIL PROTECTED] wrote: On Wed, 23 Jul 2008 13:08:03 +0100 Florent Thoumie [EMAIL PROTECTED] wrote: On Wed, Jul 23, 2008 at 12:30 PM, Olafur Osvaldsson [EMAIL PROTECTED] wrote: This is something the PR responsible introduced in his original patch... It's still present in your version. Anyway, I'm not blaming anyone, just pointing out what I think is a mistake. So this is not for the user but for the port? I'll do a swap on the tree for it, because I'm sure there are more ports doing something like: .ifndef(NO_INSTALL_MANPAGES) .. .endif The general rule of thumb is: if it doesn't begin with WITH_ or WITHOUT_, it's not user-settable. NO_INSTALL_MANPAGES is used for ports using imake that don't understand the install.man target. Now of course there are exceptions (usually for no good reason IMHO). The likes of NOPORTDOCS/NOPORTEXAMPLES/... could be changed to WITHOUT_DOCS/WITHOUT_EXAMPLES, it's just waiting for somebody to do the work. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports/125625: [PATCH] dns/nsd: USE_RC_SUBR != yes
On Wed, Jul 23, 2008 at 4:13 PM, Philip M. Gollucci [EMAIL PROTECTED] wrote: Florent Thoumie wrote: On Wed, Jul 23, 2008 at 1:12 PM, Ion-Mihai Tetcu [EMAIL PROTECTED] wrote: On Wed, 23 Jul 2008 13:08:03 +0100 Florent Thoumie [EMAIL PROTECTED] wrote: On Wed, Jul 23, 2008 at 12:30 PM, Olafur Osvaldsson [EMAIL PROTECTED] wrote: This is something the PR responsible introduced in his original patch... It's still present in your version. Anyway, I'm not blaming anyone, just pointing out what I think is a mistake. So this is not for the user but for the port? I'll do a swap on the tree for it, because I'm sure there are more ports doing something like: .ifndef(NO_INSTALL_MANPAGES) .. .endif I was talking to itectu@ about this, and figured it would be better in Mk/bsd.port.mk. The general rule of thumb is: if it doesn't begin with WITH_ or WITHOUT_, it's not user-settable. NO_INSTALL_MANPAGES is used for ports using imake that don't understand the install.man target. /me thought that was the USE_ vs WITH(OUT)?_ difference. NO* is supposed to be user settable right ? Have a look at variables in bsd.port.mk. You should have your answer. Now of course there are exceptions (usually for no good reason IMHO). The likes of NOPORTDOCS/NOPORTEXAMPLES/... could be changed to WITHOUT_DOCS/WITHOUT_EXAMPLES, it's just waiting for somebody to do the work. Heh, maybe, I kind of feel like it will get reject as a style(9) change. This is not a gratuitous change. The issue isn't to get it approved, it's to get the work done. Not having coherent namespaces leads to people using USE_GNOME=yes in /etc/make.conf and wondering why every single port depends on gnome. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to determine the date a port is installed
On Wed, Jun 11, 2008 at 8:31 AM, Peter Pentchev [EMAIL PROTECTED] wrote: On Tue, Jun 10, 2008 at 10:41:25PM -0700, Jeremy Chadwick wrote: On Wed, Jun 11, 2008 at 12:09:33AM -0500, Novembre wrote: Two questions: 1) Is it possible to determine the date a port/package is installed? ls -ld /var/db/pkg/port, use the mtime of the directory. 2) How can I delete all the ports/packages installed after a certain date? Use a combination of find with the -mtime flag, and pkg_delete. Not really. This is a bit dangerous. The dangerous part is the mtime of the directory. It would be much better to use the mtime of the +CONTENTS file, since it never changes *after* the package has been installed. It actually does if you're using portupgrade (and probably portmaster), see the @pkgdep entries. Use +DESC, +COMMENT or +MTREE_DIRS instead. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CFT: adding configuration file support to pkg_install
On Sat, May 31, 2008 at 10:05 PM, Philip M. Gollucci [EMAIL PROTECTED] wrote: Florent Thoumie wrote: This adds support for /etc/pkg.conf configuration file. Also, this adds support for naive multi-site package fetching. Any comment welcome (and appreciated). Patch is here: http://people.freebsd.org/~flz/local/ports/pkg-install-config.diff Tarball is here: http://people.freebsd.org/~flz/local/ports/pkg-install-0a553aac.tar.bz2 Hi flz, I don't quite get what the end goal is. It looks like /etc/pkg.conf is duplicating a lot of things already in /usr/ports/Mk/bsd.port.mk. Would not it be better to just have the pkg_install tools read that file instead ? I probably missed all the back story here, so feel free to put me in my place. Packages can be used without a full tree (as Kris mentioned). It can be argued that using only pkg_install to maintain packages is a PITA, but it's still possible. The fact that there's no proper tool part of or on top of pkg_install to do it is irrelevant. The multi-site package fetching is definitely something I'm interested it, but I also figured it would just iterate over the values in PACKAGESITE PACKAGESITE=ftp://foo/stdpath/base/Latest/ ftp://foo/stdpath/www/Latest where base would have things like sudo, bash, vim, etc... and could be used on multiple computers. www would have things like apache22 mod_X and would be used on 'www' class machines. I'm not sure what behaviour you're describing there. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
CFT: adding configuration file support to pkg_install
This adds support for /etc/pkg.conf configuration file. Also, this adds support for naive multi-site package fetching. Any comment welcome (and appreciated). Patch is here: http://people.freebsd.org/~flz/local/ports/pkg-install-config.diff Tarball is here: http://people.freebsd.org/~flz/local/ports/pkg-install-0a553aac.tar.bz2 -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Makefile/man page problem
On Mon, May 19, 2008 at 8:23 AM, Marc Spitzer [EMAIL PROTECTED] wrote: Hello, I am having a problem with installing/deinstalling man pages of a port I am working on, atf if interested. They are not being compressed on install and when I denistall the port I get error messages as follows: pkg_delete: file '/var/tmp/atf/man/man3/atf-c++/atf-c++-api.3.gz' doesn't exist pkg_delete: file '/var/tmp/atf/man/man3/atf-c/atf-c-api.3.gz' doesn't exist pkg_delete: file '/var/tmp/atf/man/man3/atf-sh/atf-sh-api.3.gz' doesn't exist pkg_delete: file '/var/tmp/atf/man/man4/doc/atf-test-case.4.gz' doesn't exist pkg_delete: couldn't entirely delete package (perhaps the packing list is $ find man -type f | head -5 man/man1/atf-test-program.1 man/man1/atf-config.1 man/man1/atf-cleanup.1 man/man1/atf-compile.1 man/man1/atf-exec.1 You need to set MAN1= atf-test-program.1 atf-config.1 ..., this is relative to MAN1DIR, not WRKSRC. Also, by default ATF_SHELL is set to /usr/local/bin/bash so you need to add shells/bash as a dependency if setting it to /bin/sh isn't good enough. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: lzma (Re: HEADS UP: upgrading ImageMagick to 6.4.0-6)
On Tue, Apr 22, 2008 at 11:34 AM, Andrew Pantyukhin [EMAIL PROTECTED] wrote: On Mon, Apr 21, 2008 at 02:42:24PM -0500, Brooks Davis wrote: That's well hidden (DOC/lzam.txt in the tarball). Someone should produce some sort of lzma-lite distribution that only does the basics. Then this could be a practical option. Unfortunately, a closer look dispelled the hope. The public-domained files only show how to use the GPL'ed ones. I had a conversation with the author, who is worried about incompatible formats being spawned if he releases lzma from under LGPL. He might change his mind in the future, though. So I guess we'll have to stick to using lzma from ports for now. Maybe releasing the extracting code under public domain? -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Whom do I have to bribe to get my ports committed?
On Wed, Apr 16, 2008 at 5:34 PM, Dominic Fandrey [EMAIL PROTECTED] wrote: The subject says everything: Me. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
HEADSUP: USE_NONDEFAULT_X11BASE support going away soon
Last year when X11BASE was merged with LOCALBASE, we allowed people who wanted to retain separate prefixes to do so using the USE_NONDEFAULT_X11BASE variable. This support will be removed soon (read in less than two months). Once this is done, references to X11BASE can start being removed progressively, as the ports are updated. For that reason, we ask you not to include any reference to X11BASE in your submissions from now on. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports/113132 (make -j patch)
On Wed, Mar 12, 2008 at 12:11 PM, Benjamin Lutz [EMAIL PROTECTED] wrote: This patch has been sitting in GNATS for a couple of months now: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/113132 I've received a few mails from people reporting success, and none reporting that bad things have happened. Is it possible to get this committed? It needs to go through an experimental build first. IMHO, this is an ugly hack. Ultimately, we're talking about marking almost 20k ports as parallel-safe. Why not taking the opposite approach? Allow it by default, figure out which ports break and why, fix where possible? -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports/113132 (make -j patch)
On Wed, Mar 12, 2008 at 1:01 PM, Florent Thoumie [EMAIL PROTECTED] wrote: On Wed, Mar 12, 2008 at 12:11 PM, Benjamin Lutz [EMAIL PROTECTED] wrote: This patch has been sitting in GNATS for a couple of months now: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/113132 I've received a few mails from people reporting success, and none reporting that bad things have happened. Is it possible to get this committed? It needs to go through an experimental build first. IMHO, this is an ugly hack. Ultimately, we're talking about marking almost 20k ports as parallel-safe. Why not taking the opposite approach? Allow it by default, figure out which ports break and why, fix where possible? After talking with Pav, it seems it's still the best option as the breakage rate is quite high. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Fwd: cvs commit: ports/Mk bsd.port.mk ports/devel Makefile ports/emulators/stonx Makefile ports/emulators/vmware-guestd5 Makefile ports/emulators/vmware-guestd6 Makefile ports/graphics Makefile ports/
FYI. -- Forwarded message -- From: Florent Thoumie [EMAIL PROTECTED] Date: Fri, Mar 7, 2008 at 9:47 PM Subject: cvs commit: ports/Mk bsd.port.mk ports/devel Makefile ports/emulators/stonx Makefile ports/emulators/vmware-guestd5 Makefile ports/emulators/vmware-guestd6 Makefile ports/graphics Makefile ports/graphics/dri Makefile ports/graphics/gtkdps ... To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] flz 2008-03-07 21:47:50 UTC FreeBSD ports repository Modified files: Mk bsd.port.mk develMakefile emulators/stonx Makefile emulators/vmware-guestd5 Makefile emulators/vmware-guestd6 Makefile graphics Makefile graphics/dri Makefile graphics/gtkdps Makefile graphics/mesa-demos Makefile multimedia/kaffeine Makefile www/nspluginwrapper Makefile x11-drivers/synaptics Makefile distinfo x11-fontsMakefile x11-fonts/xorg-fonts-100dpi Makefile x11-fonts/xorg-fonts-75dpi Makefile x11-fonts/xorg-fonts-cyrillic Makefile x11-fonts/xorg-fonts-miscbitmaps Makefile x11-fonts/xorg-fonts-truetype Makefile x11-fonts/xorg-fonts-type1 Makefile x11-servers Makefile x11-toolkits/gnustep-back Makefile x11-wm/gcompmgr Makefile x11-wm/kompmgr Makefile x11-wm/skippy-xd Makefile x11-wm/transset-df Makefile x11-wm/xcompmgr Makefile x11 Makefile x11/dgs Makefile x11/gsynaptics Makefile x11/kdebase3 Makefile x11/kdelibs3 Makefile x11/nvidia-driverMakefile x11/wrapper Makefile x11/xclick Makefile x11/xorg Makefile Removed files: devel/imake-4Makefile distinfo pkg-descr pkg-plist devel/imake-4/files patch-Imake.rules patch-Imakefile patch-c patch-c2 patch-d patch-imake.c patch-mkhtmlindex.pl devel/imake-4/scripts configure graphics/xfree86-dri Makefile distinfo pkg-descr pkg-plist graphics/xfree86-dri/files patch-GL-Imakefile graphics/xfree86-dri/scripts configure x11-fonts/XFree86-4-font100dpi Makefile distinfo pkg-descr pkg-plist x11-fonts/XFree86-4-font75dpi Makefile distinfo pkg-descr pkg-plist x11-fonts/XFree86-4-fontCyrillic Makefile distinfo pkg-descr pkg-plist x11-fonts/XFree86-4-fontDefaultBitmaps Makefile distinfo pkg-descr pkg-plist x11-fonts/XFree86-4-fontEncodings Makefile distinfo pkg-descr pkg-plist x11-fonts/XFree86-4-fontScalable Makefile distinfo pkg-descr pkg-plist x11-fonts/XFree86-4-fontScalable/files patch-01 patch-scaled::TTF::Imakefile x11-servers/XFree86-4-FontServer Makefile distinfo pkg-descr pkg-install pkg-plist x11-servers/XFree86-4-FontServer/files patch-programs::xfs::Imakefile xfs.sh x11-servers/XFree86-4-FontServer/scripts configure x11-servers/XFree86-4-NestServer Makefile distinfo pkg-descr pkg-install x11-servers/XFree86-4-NestServer/scripts configure x11-servers/XFree86-4-PrintServer Makefile distinfo pkg-descr x11-servers/XFree86-4-PrintServer/scripts configure x11-servers/XFree86-4-Server Makefile distinfo pkg-descr pkg-install pkg-plist x11-servers/XFree86-4-Server/files patch-CAN-2005-2495 patch-FreeBSD.cf patch-GL-Imakefile patch-HALlib_bindings.c patch-Imake.cf patch-Pci.h patch-bsdResource.c patch-bus_Imakefile patch-compiler.h patch-drm_Imakefile patch-elfloader.c patch-lib_font_FreeType_ftfuncs.c patch-lib_font_FreeType_ftfuncs.h patch-lib_font_FreeType_ftsystem.c patch-lib_font_bitmap_pcfread.c patch-loader.c patch-mga_driver.c patch-mouse.c patch-os-support_Imakefile patch-trident_driver.c patch
Re: X11/Xorg library dependencies
On Fri, Feb 8, 2008 at 7:02 PM, Gregory W. MacPherson [EMAIL PROTECTED] wrote: I just finished spending much more time than I would like to building out various library and toolkit components to get Xorg working on my FreeBSD 6.3 STABLE box. Apparently the dependency tree looks something like this: libICE libSM libXt libXext libXpm libXmu Where each library requires the ones list before it in the list. It would be nice if the owners of these various ports would update their Makefiles and Configuration scripts to check for the existence of the other ports and (gasp) actually build the missing dependencies). While some ports fail with suggestive messages, I long for the days when port maintainers understood the dependencies (rather than assuming them because they have always been on the developers' systems). You're lucky you got an answer. Next time change the tone of your email, kthxbye. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X.Org security advisory: multiple vulnerabilities in the X server
On Jan 23, 2008 3:17 AM, pluknet [EMAIL PROTECTED] wrote: This security advisory contains numerous vulnerabilities with proposed patches related to xorg-server and libXfont. Is it expected to be committed? (flz CC'ed) http://lists.freedesktop.org/archives/xorg/2008-January/031918.html http://lists.freedesktop.org/archives/xorg/2008-January/032099.html Done. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ISC DHCP Server port UID/GID question
On Jan 18, 2008 3:17 PM, Erik Van Benschoten [EMAIL PROTECTED] wrote: I noticed that, but I believe that that is a privilege separation account that is used with the OpenBSD-version of the dhclient. Also, as I pointed out, if this is usable, then why isn't the isc-dhcp-server port using it instead of allocating a UID/GID for itself during the install? There's no good reason to allocate UID/GID dynamically IMHO. This issue should be discussed with the current maintainer. In the meantime, you can set dhcpd_with(user|group) to _dhcp in /etc/rc.conf to use the base _dhcp user/group. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ISC DHCP Server port UID/GID question
On Jan 18, 2008 12:01 PM, Erik Van Benschoten [EMAIL PROTECTED] wrote: Greetings, Is there a specific reason that the port of the ISC's DHCP server does not seem to have/use a registered UID/GID? Maybe because there's already _dhcp user (uid 65) in base? -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: stale PORT - xmlrpc-c
On Dec 26, 2007 10:35 AM, Kevin 'Poof' Gerry [EMAIL PROTECTED] wrote: Hello. Just asking if you could please update the port xmlrpc-c. The current version is at 1.06.21 while the most recent version is 1.12.00. (The current version was released around mid-2006.) I updated that port to 1.06.21 a short while ago cause I needed it for xmlrpc support in rtorrent and this stable version was recent enough. 1.12.x is the advanced branch (development). Since it's not my port and I'm not familiar with it, I'm not comfortable updating the port to a potentially unstable version. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports.conf: Is there a reason behind not being default?
On Dec 18, 2007 1:54 AM, Xin LI [EMAIL PROTECTED] wrote: Hi, I think that ports-mgmt/portconf (a.k.a. /usr/local/etc/ports.conf) is a very handy feature that makes it much easier to store port options across upgrade. Is there a reason behind not making it into bsd.ports.mk? IMHO it's a big deal to take the script into ports/Tools/scripts, and move the configuration to somewhere like /etc/ports.conf... I'd rather have ports.conf being the equivalent of src.conf for ports and portconf configuration file being renamed. Whether it should be in base or not is another matter, IMHO it's a handy hack but a hack nonetheless :-) -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg 7.3: xorgcfg is missing
On Wed, 2007-10-10 at 16:43 +0200, Max Laier wrote: On Saturday 22 September 2007, Florent Thoumie wrote: Greg Rivers wrote: After upgrading to 7.3 I noticed that xorgcfg is no longer installed. It is no longer included in the x11-servers/xorg-server port, but does still appear to be installed by x11-servers/xorg-server-snap. Is this intentional? Yes, it has been removed from the build. Why - if I may ask. Is there any replacement I'm unaware of? I find it rather uncomfortable to write a xorg.conf from scratch and xorgconfig isn't the most pleaseant tool, either. Tried Xorg -configure? -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg 7.3: xorgcfg is missing
Greg Rivers wrote: After upgrading to 7.3 I noticed that xorgcfg is no longer installed. It is no longer included in the x11-servers/xorg-server port, but does still appear to be installed by x11-servers/xorg-server-snap. Is this intentional? Yes, it has been removed from the build. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg 7.3 upgrade: cyclic dependencies (fwd)
Dmitry Morozovsky wrote: FYI. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: [EMAIL PROTECTED] ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** -- Forwarded message -- Date: Fri, 14 Sep 2007 13:06:10 +0400 (MSD) From: Dmitry Morozovsky [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: xorg 7.3 upgrade: cyclic dependencies Dear colleagues, portupgrade -R xorg on RELENG_6/i386 finished, but leads to: [EMAIL PROTECTED]:/etc/mail# pkgdb -uF --- Updating the pkgdb --- Checking the package registry database Cyclic dependencies: xorg-libraries-7.3 - gtk-2.10.14_1 - dbus-1.0.2_2 - (xorg-libraries-7.3) Unlink which dependency? (? to help): Any hints? Thanks. Fixed in CVS already. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg 7.3 upgrade: cyclic dependencies (fwd)
Dmitry Morozovsky wrote: On Fri, 14 Sep 2007, Florent Thoumie wrote: FT portupgrade -R xorg on RELENG_6/i386 finished, but leads to: FT FT [EMAIL PROTECTED]:/etc/mail# pkgdb -uF FT --- Updating the pkgdb FT --- Checking the package registry database FT Cyclic dependencies: xorg-libraries-7.3 - gtk-2.10.14_1 - dbus-1.0.2_2 FT - (xorg-libraries-7.3) FT Unlink which dependency? (? to help): FT FT Any hints? Thanks. FT FT Fixed in CVS already. Ah thanks. Should I recompile gtk2 or unlink one of dependencies is enough? And I'm unsure which one. Rebuild. There's no easy way to do it otherwise. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
[Fwd: cvs commit: ports/Mk bsd.port.mk bsd.xorg.mk ports UPDATING ports/x11-drivers/xf86-input-acecad Makefile distinfo ports/x11-drivers/xf86-input-calcomp Makefile distinfo ports/x11-drivers/xf86-in
FYI. If you're experiencing any issue, please send detailed reports to [EMAIL PROTECTED] Original Message Subject: cvs commit: ports/Mk bsd.port.mk bsd.xorg.mk ports UPDATING ports/x11-drivers/xf86-input-acecad Makefile distinfo ports/x11-drivers/xf86-input-calcomp Makefile distinfo ports/x11-drivers/xf86-input-citron Makefile distinfo ... Date: Thu, 13 Sep 2007 19:45:43 + (UTC) From: Florent Thoumie [EMAIL PROTECTED] To: [EMAIL PROTECTED] flz 2007-09-13 19:45:08 UTC FreeBSD ports repository Log: - Update X.org ports to 7.3. - Mark XFree86-4 as DEPRECATED with EXPIRATION_DATE set to 2007-12-25. I hope that nobody will be bored enough on Christmas to remove them on that day. Tested by: vehemens, Rene Ladan, Beech Rintoul, sarek on x11@ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: rtorrent-0.7.4
Søren Schrøder wrote: rtorrent/libtorrent updatede to .7 (.8 unstable) * libtorrent-0.11.7.tar.gz * rtorrent-0.7.7.tar.gz configures when OPENSSL libs is specified: OPENSSL_LIBS=-L/usr/lib -ssl -crypto OPENSSL_CFLAGS=-I/usr/include compiles clean, works fine on my box ( 6.2-RELEASE-p4 ) I've updated those ports to their latest versions. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Updating X.org FreeBSD ports to 7.3
As some of you may know already, X.org released X11R7.3 yesterday. Since we already made the move to modular ports for 7.2, the work to update ports to 7.3 was much faster. It's not likely to cause any major breakage but I'd like to get some feedback (from users and pointyhat) before I commit the update, so it probably won't reach the CVS repository before wednesday. Here's a diff against current ports tree: http://dump.xbsd.org/freebsd/xorg73.diff.gz PS: I'll be away (and unreachable) getting some sunburns this week-end, so leave a message on x11@ and I'll answer when I'm back. flz 4 x11@ -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X.org update broke emulators/wine with old version of X
Gerald Pfeifer wrote: On my FreeBSD 6.2 test system with xorg-libraries-6.9.0 I am getting the following build failure after the X.org update: ../../tools/winegcc/winegcc -B../../tools/winebuild -shared ./ddraw.spec clipper.o ddraw.o ddraw_thunks.o device.o direct3d.o executebuffer.o gamma.o light.o main.o material.o palette.o parent.o regsvr.o surface.o surface_thunks.o texture.o utils.o vertexbuffer.o viewport.o version.res -o ddraw.dll.so -lole32 -luser32 -lgdi32 -ladvapi32 -lkernel32 -lntdll -ldxguid -luuid -L/usr/local/lib -R/usr/local/lib -lXext -lX11 ../../libs/port/libwine_port.a -L/files/pfeifer/porttest/wine/lib -L/usr/local/lib -Wl,-rpath,/files/pfeifer/porttest/wine/lib/wine /usr/bin/ld: cannot find -lXext winegcc: cc failed. gmake[2]: *** [ddraw.dll.so] Error 2 I believe this happens because of the changes to Mk/bsd.xorg.mk. The libraries are still there, but I assume the old /usr/X11R6/lib path is not provided any longer: % find /usr/X11R6/ -name '*libXext*' /usr/X11R6/lib/libXext.a /usr/X11R6/lib/libXext.so /usr/X11R6/lib/libXext.so.6 Can someone more familiar with this lend a helping hand, please? I assume we do want to support users still running older versions of X, don't we? Not really. This is why XFree86-4 will go away in a few months. In that case, it's not about the version of X. The breakage is caused by the PREFIX merge. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
Re: Setting X11BASE
Paul Schmehl wrote: --On May 20, 2007 5:36:26 PM -0400 Kris Kennaway [EMAIL PROTECTED] wrote: On Sun, May 20, 2007 at 04:28:56PM -0500, Paul Schmehl wrote: If you can show me where the instructions are for UPDATING a headless server that's not running xorg at all but has some xorg libraries as dependencies to other ports, I'd be happy to follow those instructions instead. All upgrade steps listed apply to all users that have any subset of X ports installed. OK. They didn't work for me. [...] I've read all the email you sent twice and haven't found what was wrong. Can you be a little more specific or give error messages? Cause blah fails just isn't enough. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
X.org 7.2 ports merged into the FreeBSD Ports Tree
As you may already know, the X11 team has been working hard for the past few months to upgrade X.org ports to 7.2. After a couple of weeks of testing, we've finally committed this upgrade. We also decided to make the PREFIX merge at the same time (moving X11BASE into LOCALBASE), which explains why there are thousands of ports affected by this commit. X.org went modular some months ago, which means that rather than releasing a few distfiles, they now have one per component (app, font, xserver, ...). What does it mean exactly for the FreeBSD user? Well, instead of having 5 ports for X.org, you'll have 255 of them? We've tried to make the upgrade as straight-forward as possible (read UPDATING) but hey, we're mere humans, we make mistakes. If you encounter any issue: re-read UPDATING, check the wiki page [1] if it's mentioned already and if it's not, send a mail to [EMAIL PROTECTED] I don't like write long mail so I'll stop here. I'd just like to thank everybody who tested things, especially those who started using the experimental git tree back in november cause things weren't that much stable at this point. I won't give a list of names to be sure I won't forget anybody, but I'll give a special mention to Kris who has been spamming my mailbox for months with all the errorlogs generated by all the experimental builds he has been running. This is a very ungrateful work but somebody has to do it. I wish your machines good luck for the next few days, cause they're gonna need it. flz for [EMAIL PROTECTED] PS: Read UPDATING. PPS: If things break badly, I'm at the beach, sipping a mojito. [1] http://wiki.freebsd.org/ModularXorg -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
Re: HEADS UP: xorg 7.2 ready for testing
Tim Bishop wrote: On Thu, May 10, 2007 at 05:28:17PM -0400, Kris Kennaway wrote: Once we have enough success reports and have dealt with all reported failures, we will proceed with the next stage, which is to import into CVS. The default sshd_config in the base system no longer works with xforwarding because the xauth program has moved. This can be fixed by setting the option: XAuthLocation /usr/local/bin/xauth It defaults to X11R6. I guess this should be fixed after the xorg merge? Shouldn't be a problem if you have the symlink from X11R6 to local. But yes, this will be fixed. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
Re: HEADS UP: xorg 7.2 ready for testing
Thierry Thomas wrote: Le Dim 13 mai 07 à 18:29:17 +0200, Thierry Thomas [EMAIL PROTECTED] écrivait : graphics/cimg is broken: this port suffers of frequent silent updates, and PORTVERSION is included in its DISTDIR, then distinfo must be updated when PORTVERSION is bumped. Same kind of problem with devel/bouml. For this port, distinfo has been updated, but the original tarball is no more fetchable from the author's site. The following patch does not fix anything for new users, but it fixes for people upgrading to x.org 7.2 and still having their distfiles: Any reason why PORTREVISION is part of DIST_SUBDIR? Cause it caused a few breakages for no apparent real benefit. Using PKGNAME to define DISTNAME or DISTFILES is also a bad thing IMO. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
Re: HEADS UP: xorg 7.2 ready for testing
Kris Kennaway wrote: On Fri, May 11, 2007 at 04:03:16AM +0400, Andrew Pantyukhin wrote: On 5/11/07, Edwin Groothuis [EMAIL PROTECTED] wrote: On Thu, May 10, 2007 at 05:28:17PM -0400, Kris Kennaway wrote: Dear porters, We are now ready for xorg 7.2 testing! Over the past week we have done extensive tests of various upgrade scenarios, fixed many remaining bugs, and now the upgrade is looking good. Of course, we can't possibly test everything, so that's where you come in. What we need now is for everyone to download this tarball: http://people.freebsd.org/~kris/ports-xorg-7.2.tbz http://people.FreeBSD.org/~ade/ports-xorg-7.2-nogit.tar.bz2 is only 28Mb http://people.freebsd.org/~sat/diffs/ports.xorg72.diff.bz2 is only 461 Kb In fact, that's what we've been promised - a diff :-) Dunno who promised this to you, but it was never the plan. Was about to say the same. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
Re: HEADS UP: xorg upgrade plans
Ken Yamada wrote: From: Rene Ladan [EMAIL PROTECTED] Currently most development happens in the git repository. You can look at http://git.xbsd.org/?p=freebsd/ports.git;a=summary to see what goes on. No, http://wiki.freebsd.org/ModularXorg; says; --Quote-- Disclaimer If you read about the git repository, forget about it and hold your breath a couple days again. Everything should be merged back to the FreeBSD within a few days. --Unqote-- git may be maintained, but the page already does not show any of git pages and information, anymore. That is the reason why I am asking... We're committing a last round of fixes and will submit a tarball for testing hopefully tonight or tomorrow. As soon as we'll get enough success reports, we'll go all-in. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
Re: xorg merge and git
Andriy Gapon wrote: One question: will the ports still be accessible via git after the merge of modular xorg branch ? I started to like git very much (as a distribution tool), it seems to be much faster than cvsup. Probably not, at least not the xorg branch. I'm hosting this tree on a personal server and while it doesn't bother me to use bandwidth for that, I can't tell it will stay there forever (I'll probably upgrade the server soon, so the tree will be dropped and recreated) so I'm not really comfortable seeing people using it as a day to day replacement for portsnap (which IMHO is much faster, if you're not doing any development). -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committe signature.asc Description: OpenPGP digital signature
Reviewing changes before the merge of X.org 7.2
As you may know, we're not far from merging xorg modular in the CVS repository. Before this happens, we have to make sure there are no collateral damages made to innocent ports. I'd like people to come to #freebsd-xorg on EFNet this week-end and coordinate to review this diff [1], so that we don't duplicate the effort more than once. So come, pick a category (say games), say you're going to review it on the channel, then have fun. Obviously you can do that for more than one category. Most of the changes made to existing ports (besides xorg itself and mesa) should be pretty straight-forward like fixing plist issues due to prefix merge, setting USE_GL when it's not, ... so it shouldn't take that long, assuming I'm not alone with miwi. Anyway, the more who comes, the quicker it will be. Thanks. [1] http://nikki.xbsd.org/xorg-bigdiff-20070410.diff.gz -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
Inclusion of Intel PRO/Wireless LAN 2100/2200/2915 firmwares in the base system
FYI. FreeBSD -CURRENT users with ipw(4) or iwi(4) will have to set legal.intel_driver.license_ack=1 in /boot/loader.conf after making sure they agreed to Intel LICENSE file located in /usr/share/doc/legal/intel_driver (where driver is ipw or iwi). Ports will be marked as IGNORE for OSVERSION = 700032 in a few minutes. I'd like to thank Andrew Wilson once again for the dedication he showed in getting things done. PS: Before you ask, wpi(4) (Intel PRO/Wireless LAN 3945) firmware will also be included once the driver hits the tree. -- flz 2007-03-02 11:42:56 UTC FreeBSD src repository Modified files: etc/mtreeBSD.usr.dist share/docMakefile sys/modules Makefile sys/sys param.h sys/toolsfw_stub.awk sys/conf kmod.mk Added files: share/doc/legal Makefile share/doc/legal/intel_ipw Makefile share/doc/legal/intel_iwi Makefile sys/contrib/dev/ipw LICENSE ipw2100-1.3-i.fw.uu ipw2100-1.3-p.fw.uu ipw2100-1.3.fw.uu sys/contrib/dev/iwi LICENSE ipw2200-bss.fw.uu ipw2200-ibss.fw.uu ipw2200-sniffer.fw.uu sys/modules/ipwfwMakefile sys/modules/ipwfw/ipw_bss Makefile sys/modules/ipwfw/ipw_ibss Makefile sys/modules/ipwfw/ipw_monitor Makefile sys/modules/iwifwMakefile sys/modules/iwifw/iwi_bss Makefile sys/modules/iwifw/iwi_ibss Makefile sys/modules/iwifw/iwi_monitor Makefile Log: - Add Intel firmwares for Intel PRO/Wireless LAN 2100/2200/2915 cards in a uuencoded format along with their respective LICENSE files. - Add new share/doc/legal directory to BSD.usr.dist mtree file. This is the place we install LICENSE files for restricted firmwares. - Teach firmware(9) and kmod.mk about licensed firmwares. Restricted firmwares won't load properly unless legal.name.license_ack is set to 1, either via kenv(1) or /boot/loader.conf. Reviewed by:mlaier, sam Permitted by: Intel (via Andrew Wilson) MFC after: 1 month Revision ChangesPath 1.325 +2 -0 src/etc/mtree/BSD.usr.dist 1.21 +1 -1 src/share/doc/Makefile 1.1 +6 -0 src/share/doc/legal/Makefile (new) 1.1 +7 -0 src/share/doc/legal/intel_ipw/Makefile (new) 1.1 +7 -0 src/share/doc/legal/intel_iwi/Makefile (new) 1.215 +6 -1 src/sys/conf/kmod.mk 1.1 +207 -0src/sys/contrib/dev/ipw/LICENSE (new) 1.1 +4678 -0 src/sys/contrib/dev/ipw/ipw2100-1.3-i.fw.uu (new) 1.1 +4574 -0 src/sys/contrib/dev/ipw/ipw2100-1.3-p.fw.uu (new) 1.1 +4857 -0 src/sys/contrib/dev/ipw/ipw2100-1.3.fw.uu (new) 1.1 +210 -0src/sys/contrib/dev/iwi/LICENSE (new) 1.1 +4459 -0 src/sys/contrib/dev/iwi/ipw2200-bss.fw.uu (new) 1.1 +4337 -0 src/sys/contrib/dev/iwi/ipw2200-ibss.fw.uu (new) 1.1 +4386 -0 src/sys/contrib/dev/iwi/ipw2200-sniffer.fw.uu (new) 1.519 +5 -0 src/sys/modules/Makefile 1.1 +7 -0 src/sys/modules/ipwfw/Makefile (new) 1.1 +15 -0 src/sys/modules/ipwfw/ipw_bss/Makefile (new) 1.1 +15 -0 src/sys/modules/ipwfw/ipw_ibss/Makefile (new) 1.1 +15 -0 src/sys/modules/ipwfw/ipw_monitor/Makefile (new) 1.1 +7 -0 src/sys/modules/iwifw/Makefile (new) 1.1 +15 -0 src/sys/modules/iwifw/iwi_bss/Makefile (new) 1.1 +15 -0 src/sys/modules/iwifw/iwi_ibss/Makefile (new) 1.1 +15 -0 src/sys/modules/iwifw/iwi_monitor/Makefile (new) 1.286 +1 -1 src/sys/sys/param.h 1.6 +30 -4 src/sys/tools/fw_stub.awk -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
Beryl/Compiz ports looking for a maintainer
Hey list, As you know, (at some point) we're working on X.org 7.2 in a different repository. At the moment I have (almost) working ports for compiz and beryl. I currently maintain them but it's taking more time than I want to allow it. Furthermore, I don't want to maintain them when it's going to hit the FreeBSD ports collection and I'm not going to add it without a maintainer set. I first thought I would add it to the list of ports maintained by x11@ but we/they have enough work to do with the current set. So, I'm looking for a maintainer who is responsive, careful, and I guess it's better if he's a committer (but that's not mandatory). If you're interested and already using my git tree, that's a big plus. I'm working at updating beryl ports to 0.1.99.2 (and will probably work on the 0.2.0 update) but I hope this is the last one, cause time spent on beryl ports isn't spent on something else. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
Re: REPLACES variable in Makefile ?
Andrew Pantyukhin wrote: On 1/30/07, Alagarsamy [EMAIL PROTECTED] wrote: I want to know whether we are having REPLACES variable just like CONFLICTS variable in the Makefile ? I have two packages A and B. Package A is already installed. I want to install package B which should automatically replace the package A. In case, if there is no REPLACES variable, is there any other way to do this ? Your end-user desire is clear, but if you want to go a bit further and propose a solution you should probably examine systems where this already works (I'd start with debian). Currently in ports, you just have to bark at users to perform some actions manually. Nobody barks here. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
Re: Remaining X11BASE build failures
Kris Kennaway wrote: After another build with X11BASE=/usr/xorg, these are the remaining ports with build failures: 233 ! Jan 11 User Ports-i386 ( 124) endeavour-1.13.0_2 failed on i386 5-exp 335 ! Jan 12 User Ports-i386 (1007) gcc-withgcjawt-4.1.2_20070108 failed on i386 5-exp 336 ! Jan 12 User Ports-i386 (1006) gcc-withgcjawt-4.2.0_20070102 failed on i386 5-exp 385 ! Jan 11 User Ports-i386 ( 870) gpsdrive-2.09_5 failed on i386 5-exp 412 ! Jan 11 User Ports-i386 ( 230) gtkdps-0.3.4 failed on i386 5-exp 452 ! Jan 11 User Ports-i386 (1001) hs-hgl-2.0.4_2 failed on i386 5-exp 832 ! Jan 12 User Ports-i386 ( 469) mugshot-1.1.30 failed on i386 5-exp 934 ! Jan 11 User Ports-i386 (1033) openoffice.org-1.0.3_7 failed on i386 5-exp 935 ! Jan 12 User Ports-i386 (1035) openoffice.org-1.1.5.20061219 failed on i386 5-exp 936 ! Jan 12 User Ports-i386 (1033) openoffice.org-1.1.5_4 failed on i386 5-exp 1095 ! Jan 11 User Ports-i386 ( 158) plan9port-20060629 failed on i386 5-exp 1247 ! Jan 11 User Ports-i386 ( 687) raop_play-0.5.1 failed on i386 5-exp 1364 ! Jan 11 User Ports-i386 ( 197) sjog-0.5_2 failed on i386 5-exp 1365 ! Jan 10 User Ports-i386 ( 96) ski-0.943l.2 failed on i386 5-exp 1430 ! Jan 11 User Ports-i386 ( 621) ted-2.17 failed on i386 5-exp 1501 ! Jan 11 User Ports-i386 (1002) vim+ruby-7.0.178_4 failed on i386 5-exp 1502 ! Jan 11 User Ports-i386 (1002) vim-7.0.178_3 failed on i386 5-exp Can you also add that maintainers failing to fix these issues won't be able to complain if some random committer pass by and fix them? I think you've sent enough email now so that responsible maintainers should have fixed them long ago. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
Re: Recommended test ordering question.
Kris Kennaway wrote: On Sun, Jan 14, 2007 at 10:33:07PM +0100, Julien Gabel wrote: Hello, I just updated the patch for a little port i maintained, and encountered a curious error following the Recommended test ordering found in the FreeBSD Porter's Handbook to test it properly. Here are the steps: - make install = ok. - make package = ok. - make deinstall = ok. - pkg_add package-name = ok. - make deinstall = Errors about directories which can't be deleted. = Directories _not_ present anymore, but were present after the pkg_add step. = ok (port seems deinstalled correctly). - make reinstall = ok. - make package = ok. Any suggestion on why i get these errors, although all seems fine? Your pkg-plist is incorrect. Perhaps you are doing things in your post-install script that are only executed when the port makefile is run, but do not have a corresponding @exec statement in your pkg-plist. [...] or the make install step might also create empty directories. You should add those with @exec mkdir -p %D/share/foo in the packing list. Note that these steps won't tell you if you have installed files not recorded in the packing list. Using PREFIX=/tmp/foo usually help, assuming it is prefix-clean. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
Re: Wifi driver General Question
Waleed Harbi wrote: Hi Everyone, I have not seen FreeBSD packages has Intel ipw3945 wireless driver Intel® PRO/Wireless 3945ABG Driver: http://www.freebsd.org/cgi/ports.cgi?query=ipwstype=name http://www.freebsd.org/cgi/ports.cgi?query=ipwstype=name Because there's no such driver in ports. You can get one here but I'm not maintaining it: http://people.freebsd.org/~flz/local/wpi/ I am looking to install it on my laptop and the above driver is my laptop diver the source code of driver is below: http://ipw3945.sourceforge.net/ Yeah that's the Linux version. General Question: I have USB camera on my laptop built in, Is FreeBSD support this kind of camera? Well, can't really tell without knowing the type of camera, but the answer is probably no. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
Bugathon Episode 2
As announced last week, we're having a bug party on #freebsd-bugbusters @ EFNET this week end. So if you feel like fixing a few bugs, or just talking a bit with us, join the channel anytime! Gcc 4.1 is being tested on the cluster and it affects a couple (*sic*) of ports, so we'd appreciate any help to fix those. Anyway, have a nice week end! -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
(Bug|Port)athon next weekend (Dec. 16/17)
Hey folks, We're going to hold the next (bug|port)athon next weekend. Same place as usual (@freebsd-bugbusters on EFNet). As you may know, some of our ports committers have been working hard on fixing ports to be X11BASE-clean so that the PREFIX merge can be done without (too much) hassle. Anyway, work isn't finished and we could probably use your help. The ports PR count is approximately 815 and we could easily do better than that, so join IRC next weekend and help us close some of those PRs. Cheers. PS: A PR a day keeps the doctor away. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
HEADSUP: Imminent removal of XFree86-3 from the ports
Hi folks, As you may know we're in the middle of testing the new X.org 7.2-RC2 on the cluster and it's time to make some cleanup in our X11 ports. The x11/XFree86-3 has been deprecated for quite some time now and will be removed within a few days, so I can only recommend switching now, and not waiting for the port to be actually removed. While you will be upgrading, I also recommend upgrading to X.org rather than XFree86-4 cause we will deprecate the x11/XFree86-4* ports at the same time (giving a 6 months time period to make the switch to X.org). So unless you have a very good reason to stay with XFree86-4, don't do it. There might still be driver issues with X.org so if you're aware of such things, please contact the X.org developers so they can fix it upstream. On behalf of the x11@ team. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
Re: xorg 7.x and non-standard X11BASE
Kris Kennaway wrote: On Tue, Nov 28, 2006 at 08:44:25PM +, Florent Thoumie wrote: Joel Dahl wrote: On Tue, 2006-11-28 at 18:24 +, Florent Thoumie wrote: Doug Barton wrote: Currently we have 2 locations for files installed by ports. LOCALBASE (which defaults to /usr/local) and X11BASE (which defaults to /usr/X11R6). When xorg 7 is imported, it will be installing into /usr/local. I don't know where you guys read that. Well, some of us might remember http://lists.freebsd.org/pipermail/freebsd-ports/2006-July/033964.html I've been talking to Dejan at that time but I can't remember if I actually meant that we were going to add new X.org directly in LOCALBASE. Though I haven't tried to contact him for a while, I guess he's been busy with other things these days. I somehow inherited a x11 hat and IMHO, it would be better to move to LOCALBASE after we moved everything else and made sure all ports were X11BASE-clean. I guess I was also mistaken about the intentions as well. I actually thought of moving everything but libs and fonts to LOCALBASE. ... but if miwi manages to fix all non X11BASE-clean ports and move them to LOCALBASE within a month then we can install the complete X.org 7.2 distribution in LOCALBASE :-) Anyway, the good news is that there are only a few hundred X11BASE-unclean errors (less than I'd thought), so this is something we can keep pushing on for now. I guess the next exp-build will be with X11BASE set to LOCALBASE then. Note: We might get runtime problems if some hardcoded /usr/X11R6 remain in source files though. -- Florent Thoumie signature.asc Description: OpenPGP digital signature
Re: xorg 7.x and non-standard X11BASE
Doug Barton wrote: Currently we have 2 locations for files installed by ports. LOCALBASE (which defaults to /usr/local) and X11BASE (which defaults to /usr/X11R6). When xorg 7 is imported, it will be installing into /usr/local. I don't know where you guys read that. Shortly thereafter the plan is to do away with the X11BASE stuff altogether, and have all ports install into /usr/local. This should happen before we move X.org to LOCALBASE. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
Re: xorg 7.x and non-standard X11BASE
Doug Barton wrote: Florent Thoumie wrote: Doug Barton wrote: Currently we have 2 locations for files installed by ports. LOCALBASE (which defaults to /usr/local) and X11BASE (which defaults to /usr/X11R6). When xorg 7 is imported, it will be installing into /usr/local. I don't know where you guys read that. Well, feel free to correct me if I'm wrong, but I thought that was the plan? Well, unless somebody with a hat tells me to do it, I definitely won't :-) Shortly thereafter the plan is to do away with the X11BASE stuff altogether, and have all ports install into /usr/local. This should happen before we move X.org to LOCALBASE. Cool, I wasn't sure about the ordering on that, but one virtue of installing xorg 7 into LOCALBASE would be that you don't have to move all the current X11BASE ports all at once, since most things would just work. But you end up with real X11 stuff in LOCALBASE and some other stuff in X11BASE while everything is being moved. This is a bit confusing. Anyway, we've have X11 in X11BASE for quite a few years now, it can wait two months before we move it :-) For example, when I installed my new laptop I put X11BASE=/usr/local in /etc/make.conf, and everything worked fine, including a bunch of the ports that were broken when kris did his recent /usr/xorg run. I did the same on all my machine, had only a couple of mtree problems, otherwise it was just fine. In any case, none of this is material to the OP's question. Fixing the ports now to install into a non-standard base will make them PREFIX clean down the road no matter where PREFIX happens to be. :) True enough, once we fixed all ports to be PREFIX-clean and X11BASE-clean, X.org move will just be a matter of removing one line in bsd.xorg.mk and bumping PORTREVISIONs. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
Re: New portmgr member: Pav Lucistnik
Erwin Lansing wrote: Portmgr is pleased to announce that Pav Lucistnik has accepted the challenge of being a portmgr member. Pav has been with the project for a long time and is one of our most active committers and bug busters. He has been working on the ports infrastructure and will now be working with the other portmgr members on integrating infrastructure patches and quality assurance in addition to other portmgr tasks. Wish him luck! Oook! Woot! \o/ -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
Re: UID/GID dynamic allocation in net/isc-dhcp3-server: why?
Kris Kennaway wrote:
On Sat, Nov 11, 2006 at 10:05:05PM +0100, Simon L. Nielsen wrote:
On 2006.11.11 15:48:05 -0500, Kris Kennaway wrote:
On Sat, Nov 11, 2006 at 09:37:31PM +0100, Simon L. Nielsen wrote:
On 2006.11.11 21:12:09 +0200, Dmitry Pryanishnikov wrote:
I don't like the current behaviour of the net/isc-dhcp3-server port
of creating 'dhcpd' user and group using dynamic allocation instead of
having static one (as specified in /usr/ports/{U,G}IDs). I like the idea
of [ug]id ranges, and dynamic allocation doesn't keep within this idea
(ids of users and daemons get mixed). Is there specific reason why there
is no static [ug]id for net/isc-dhcp3-server?
Personally I have it precisely the other way around - I find the
static allocations rather annoying since they are bound to collide
with existing UID's at some point.
IMO the optimal solution would be to have some magic which auto
assigns ports/system UID/GID's from different ranges that normal
users.
Just so :)
UIDs below 1000 are (and have been for many years) allocated to the
system (ports/src), and are not supposed to be allocated by
administrators. This at least works out of the box with some of the
tools we have for allocating new users, so are you aware of any that
don't do this?
I know that people are not suposed to use 1000 and for normal users
and I havent seen any FreeBSD tools which uses low UID's for normal
users by default. I don't do use low UID's new systems/sites, but
sometimes you have old systems/sites where that is just not the
case. I'm certainly not saying we should bent over backwards to
support these legacy systems, I just want to point out that they do
exist. I'm really not trying to start a big debate over static
vs. dynamic UID/GID allocations, the original mail just made it sound
to me like it was a universal truth that ports should use hardcoded
UID/GID's and it was always a good thing.
And the site where I have UID/GID's in the 1000 range is called
FreeBSD.org :-) (we use UID/GID's from 500 and up).
I dunno what you are suggesting could be done on systems where the
administrators have chosen to ignore the conventions. Even supposing
the 1000 range was dynamically remapped to some other range on such
systems, what's to stop the rogue admin from allocating there too?
I have a bsd.port.mk patch in the works to create users/groups
automatically from uids/gids registered in the related files. It
wouldn't be too hard to include a UID_OFFSET/GID_OFFSET parameter so
that the local admin can reserve uids/gids in say range 2000-3000
instead of 0-1000 (which isn't really 0-1000 but I'm too lazy to check
where system uids/gids stop :-)
Would it be alright with you Simon?
--
Florent Thoumie
[EMAIL PROTECTED]
FreeBSD Committer
signature.asc
Description: OpenPGP digital signature
Re: Bugathon, yeah it's time again
On Fri, 2006-11-03 at 22:03 +, Florent Thoumie wrote: I hereby declare open the holy bugathon! We're closing the bugathon with the following numbers: - ports: 108 - doc: 33 - usb: 1 Due to technical problems we've closed less PRs than during the last bugathon, but it didn't make the event any less useful. It doesn't appear here but progress has been made on xorg-modular front, thanks to people reporting bugs on x11@ or directly to me. If you're interested in trying it, please refer to the ModularXorg page on the FreeBSD Wiki [1]. Anyway I'd like to thank each and every committer/participant who joined the channel during the week end. I hope to see even more people during next event. Happy bugbusting! [1] http://wikitest.freebsd.org/ModularXorg -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: This is a digitally signed message part
Re: Bugathon, yeah it's time again
On Fri, 2006-10-27 at 18:13 +0100, Florent Thoumie wrote: Ok, heads up folks. Ports have been frozen for some weeks now, and it's only a matter of time before ice starts melting. So we're planning to hold the next bugathon next week end (well, in one week). Same server, same channel (#freebsd-bugbusters @ EFNET), you have one week to grab a list of PR and start working on them. WWW: http://wikitest.freebsd.org/Bugathons/November2006 Note: Since I still don't receive much feedback from src-committers, I expect it to be mainly ports-related. Obviously I may be wrong and there will probably a few src-committers coming, this channel is still a good place to discuss bugs. I hereby declare open the holy bugathon! -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: This is a digitally signed message part
