Re: Proposal moving *spell dicts to ports/textproc/*spell/dicts
2010/12/4 Thierry Thomas :
> Le sam 4 déc 10 à 11:58:44 +0100, David DEMELIER
> écrivait :
>> Hi,
>
> Hello,
>
>> As I said some weeks ago I personally don't like much the use of
>> ports/{french,chinese,whatever}/ directories. I saw that openbsd
>> created sub directories in the aspell port. I think this is a really
>> good idea, it's really easier to find.
>>
>> I don't think german/ispell french/aspell textproc/gu-aspell are
>> really easy to find.
>>
>> I propose creating a ports/textproc/aspell/dicts and same for
>> textproc/ispell and textproc/hunspell and moving every spellings ports
>> to these directories.
>
> I don't know about hunspell and ispell, but aspell's dictionaries are
> maintained and updated independently, at different dates: its why these
> are separate ports.
>
> Regards,
> --
> Th. Thomas.
>
Yes but I don't want to make one big dict/ port. I would like to move
all aspell languages ports into aspell/dicts/ and then you go under
ports/textproc/aspell/dicts/fr && make install for example :)
Cheers,
--
Demelier David
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: packages compressed with xz
On Sat, Dec 04, 2010 at 11:19:21PM +0100, Simon L. B. Nielsen wrote: > > On 30 Nov 2010, at 03:16, jhell wrote: > > > Agreed. Soon can be quantified by actual need and of which there is not > > much need except for larger packages but adding this would just add > > unneeded complication to the system that is already in place. > > > We are running out of diskspace on event the FTP master site - > currently we are at ~1TB. The xz compression gives as significant > space saving - so there is already a need. > > PS. anyone saying a 1 TB etc. disk is cheap will be ignored. And all ftp mirror admins will be very grateful to sync smaller .xz packages. :) pgpADHhbR7zTC.pgp Description: PGP signature
Re: emacs and gconf troubles
Hi Andrea, Andrea Venturoli writes: > Hello. > I'm having a small, low priority, trouble; more an annoyance in fact. > Since a while, if I start an X11 emacs from a terminal window, after I > close emacs, the terminal window won't close with Ctrl-D; I have to > close the terminal windows by hand. > With the latest upgrade, I see the following warning at emacs startup: >> (emacs:2267): GLib-WARNING **: In call to g_spawn_sync() >> exit status of a child process was requested but SIGCHLD >> action was set to SIG_IGN and ECHILD was received by >> waitpid(), so exit status can't be returned. This is a bug >> in the program calling g_spawn_sync(); either don't request >> the exit status, or don't set the SIGCHLD action. >> GConf Error: Failed to contact configuration server; some >> possible causes are that you need to enable TCP/IP networking >> for ORBit, or you have stale NFS locks due to a system crash. >> See http://projects.gnome.org/gconf/ for information. >> (Details - 1: Failed to get connection to session: Command >> line `dbus-launch --autolaunch=b3fbd8cb89ee22fd22fc29261a5f >> --binary-syntax --close-stderr' exited with non-zero exit status >> 3429110: ) >> >> (emacs:2267): GLib-WARNING **: In call to g_spawn_sync(), exit >> status of a child process was requested but SIGCHLD action was set >> to SIG_IGN and ECHILD was received by waitpid(), so exit status >> can't be returned. This is a bug in the program calling >> g_spawn_sync(); either don't request the exit status, or don't set the >> SIGCHLD action. > I really don't understand what I should check... > Any help is appreciated. How're you starting X server ? And with which version are you seeing this behaviour ? And are you running GNOME, KDE, or any desktop environment ? Thanks -- Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 freebsd.org!ashish | http://people.freebsd.org/~ashish/ Avoid Success At All Costs !! pgpqlcSyYTuqW.pgp Description: PGP signature
x264 & gcc44 on amd64 -- and "generic" question about gccXX ports
Hello, Freebsd-ports. Does somebody success in building x264 on amd64 host? It needs gcc44, which is marker "BROKEN", and doesn't build in Fortran part, indeed, but maybe fix known? Also, why we have `lang/gcc4x' ports without OPTIONS or subports for fortran, obj-c, java? -- // Black Lion AKA Lev Serebryakov ___ 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/152823: Request for new port: projectM
Synopsis: Request for new port: projectM Responsible-Changed-From-To: freebsd-amd64->freebsd-ports Responsible-Changed-By: avg Responsible-Changed-When: Sun Dec 5 14:37:50 UTC 2010 Responsible-Changed-Why: Reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=152823 ___ 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: amd64/152823: Request for new port: projectM
The following reply was made to PR ports/152823; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, rank1see...@gmail.com Cc: Subject: Re: amd64/152823: Request for new port: projectM Date: Sun, 05 Dec 2010 16:36:43 +0200 This is a ports PR, not for amd64 kernel architecture. If you are interested in a port of software, the best way to get it is to write it yourself (that's just stating the fact). This could be useful: http://www.freebsd.org/doc/en/books/porters-handbook/ -- Andriy Gapon ___ 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: Proposal moving *spell dicts to ports/textproc/*spell/dicts
> > Hello,
> >
> >> As I said some weeks ago I personally don't like much the use of
> >> ports/{french,chinese,whatever}/ directories. I saw that openbsd
> >> created sub directories in the aspell port. I think this is a really
> >> good idea, it's really easier to find.
> >>
> >> I don't think german/ispell french/aspell textproc/gu-aspell are
> >> really easy to find.
> >>
> >> I propose creating a ports/textproc/aspell/dicts and same for
> >> textproc/ispell and textproc/hunspell and moving every spellings ports
> >> to these directories.
> >
> > I don't know about hunspell and ispell, but aspell's dictionaries are
> > maintained and updated independently, at different dates: its why these
> > are separate ports.
> >
> > Regards,
> > --
> > Th. Thomas.
> >
>
> Yes but I don't want to make one big dict/ port. I would like to move
> all aspell languages ports into aspell/dicts/ and then you go under
> ports/textproc/aspell/dicts/fr && make install for example :)
>
> Cheers,
>
> --
> Demelier David
Problem:
Scripts assuming 2 levels for all ports.
Paths such as */*/pkg-plist would no longer be complete.
Cheers,
Julian
--
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
Mail plain text; Not quoted-printable, or HTML or base 64.
Avoid top posting, it cripples itemised cumulative responses.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: packages compressed with xz
On Fri, 03 Dec 2010 23:07:51 +0200 Volodymyr Kostyrko wrote: > 30.11.2010 04:40, Julien Laffaye wrote: > > You can specify limits during compression, so the question is > > should we do that so that hosts with N MB of RAM can decompress > > packages? Do we retain the compression ratio over bzip2 if we > > limit compression memory to 512 MB so that decompression would be > > possible with, say, 128 MB? > > > > According to xz(1), in its default mode (-6), xz uses ~100MiB for > > compression and ~10MiB for decompression. > > That seems to be acceptable. > > You possibly miss something about compression/decompression. > > The designated memory size is not directly affected only by > compression mode. When decompressing you will need memory for: > > 1. Data history. > 2. Dictionary. > 3. Some indexes. > > And those ones are all empty at start. So say, if you are compressing > something really huge trying to use 4G of memory you end using that > much memory between 2G - 3G of source data. And we will need 512MB to > decompress that hunk of data. > > Are the packages _that_ large? [ .. ] The biggest package that can be produced by a port it's a bit over 10G. -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: FreeBSD Port: davical-0.9.9.3
I don't think that you loose your data, as it is stored in the pgsql database which is not replaced by the package. Anyhow, it is always good to have a backup. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: packages compressed with xz
> The biggest package that can be produced by a port it's a bit over 10G. > Curious - which one? -- Eitan Adler ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: packages compressed with xz
Eitan Adler writes: > > The biggest package that can be produced by a port it's a bit over 10G. > > Curious - which one? OpenOffice(-3)? Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: packages compressed with xz
>> >> Curious - which one? > > OpenOffice(-3)? He told me on IRC - something in games/ $grep -R "NO_PACKAGE" /usr/ports/games :-) -- Eitan Adler ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: packages compressed with xz
On Sun, 5 Dec 2010 11:41:29 -0500 Eitan Adler wrote: > >> > >> Curious - which one? > > > > OpenOffice(-3)? > > He told me on IRC - something in games/ > > $grep -R "NO_PACKAGE" /usr/ports/games :-) Hum, looks like either they got smaller or QAT doesn't have all the games packages built yet: -rw-r--r-- 1 root wheel 5.3G Nov 29 02:42 crafty-tablebase-pawn-20070910.tbz -rw-r--r-- 1 root wheel 1.7G Nov 29 01:59 crafty-tablebases-no-pawn-20070910.tbz -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: packages compressed with xz
05.12.2010 18:03, Ion-Mihai Tetcu wrote: And those ones are all empty at start. So say, if you are compressing something really huge trying to use 4G of memory you end using that much memory between 2G - 3G of source data. And we will need 512MB to decompress that hunk of data. Are the packages _that_ large? [ .. ] The biggest package that can be produced by a port it's a bit over 10G. 0k, I'll try to be sharper. How many of that huge packages will run on a prehistoric cpu/64Mb mem combo? I'll bet even working with the OpenOffice will be... challenging. Let's take the other route. Packages that large will benefit from maximum xz compression most. The question clearly is "Would we like to ditch maximum compression for those huge ones taking care of the hardware that would never be ready to run them?" Don't listen to me anyway. Our first goal is clearly making FreeBSD work everywhere. Capping the xz limits would do nothing for me personally because all of my machines are capable of building any software I want - I don't use packages at all. So I don't have a right to vote. We should think from the point of people running that hardware. And I think we should support them. -- Sphinx of black quartz judge my vow. ___ 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: x264 & gcc44 on amd64 -- and "generic" question about gccXX ports
Quoth Lev Serebryakov on Sunday, 05 December 2010: > Hello, Freebsd-ports. > > Does somebody success in building x264 on amd64 host? It needs > gcc44, which is marker "BROKEN", and doesn't build in Fortran part, > indeed, but maybe fix known? > > Also, why we have `lang/gcc4x' ports without OPTIONS or subports for > fortran, obj-c, java? > > -- > // Black Lion AKA Lev Serebryakov > > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" I built x264 fine on amd64, and I do not have gcc44 installed. My gcc -v reports: Using built-in specs. Target: amd64-undermydesk-freebsd Configured with: FreeBSD/amd64 system compiler Thread model: posix gcc version 4.2.1 20070719 [FreeBSD] -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com pgpHRiVKJpA76.pgp Description: PGP signature
Re: x264 & gcc44 on amd64 -- and "generic" question about gccXX ports
Hello, Chip. You wrote 5 декабря 2010 г., 20:58:23: > I built x264 fine on amd64, and I do not have gcc44 installed. My gcc -v > reports: It is optional, and installing gcc46 before (by hands) helps. -- // Black Lion AKA Lev Serebryakov ___ 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: emacs and gconf troubles
Andrea Venturoli 쓰시길: > Hello. > I'm having a small, low priority, trouble; more an annoyance in fact. > > Since a while, if I start an X11 emacs from a terminal window, after I > close emacs, the terminal window won't close with Ctrl-D; I have to > close the terminal windows by hand. > > With the latest upgrade, I see the following warning at emacs startup: > >> (emacs:2267): GLib-WARNING **: In call to g_spawn_sync() >> exit status of a child process was requested but SIGCHLD >> action was set to SIG_IGN and ECHILD was received by >> waitpid(), so exit status can't be returned. This is a bug >> in the program calling g_spawn_sync(); either don't request >> the exit status, or don't set the SIGCHLD action. >> GConf Error: Failed to contact configuration server; some >> possible causes are that you need to enable TCP/IP networking >> for ORBit, or you have stale NFS locks due to a system crash. >> See http://projects.gnome.org/gconf/ for information. >> (Details - 1: Failed to get connection to session: Command >> line `dbus-launch --autolaunch=b3fbd8cb89ee22fd22fc29261a5f >> --binary-syntax --close-stderr' exited with non-zero exit status >> 3429110: ) >> >> (emacs:2267): GLib-WARNING **: In call to g_spawn_sync(), exit >> status of a child process was requested but SIGCHLD action was set >> to SIG_IGN and ECHILD was received by waitpid(), so exit status >> can't be returned. This is a bug in the program calling >> g_spawn_sync(); either don't request the exit status, or don't set the >> SIGCHLD action. > > I really don't understand what I should check... > Any help is appreciated. There is no trouble if you run Emacs on GNOME desktop, IMHO. Still you don't have GNOME, please go ahead.. # pkg_add -v -r ... Sincerely, -- 소여물 황병희(黃炳熙) | .. 출항 15분전.. "Santino, never let anyone outside the family know what you are thinking." -- Vito Corleone, "Chapter 2", page 75 pgpUH1FJRh3pN.pgp Description: PGP signature
FreeBSD Port: sql-ledger-2.8.23
Dear FreeBSD ports administrator(s), I recently installed the FreeBSD port 'sql-ledger-2.8.23' when i came across this article: *http://tinyurl.com/2v6g94f* Can you please comment on the security flaws that where found in this port? Are these vulnerabilities also relevant to version 2.8.23? This is important to me because i want to use this software for accounting purposes from the internet; in other words outside the intranet (business). Any comment you may have is helpful, i think. Thanks in advance, Sincerely, L. Derksen Netherlands p.s; happy FreeBSD user for years now ;) Many thanks to the whole FreeBSD team! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: sql-ledger-2.8.23
On 5 December 2010 17:05, L. Derksen wrote: > Dear FreeBSD ports administrator(s), > > > I recently installed the FreeBSD port 'sql-ledger-2.8.23' when i came across > this article: > > *http://tinyurl.com/2v6g94f* > > Can you please comment on the security flaws that where found in this port? > Are these vulnerabilities also relevant to version 2.8.23? Almost certainly. You could update the port yourself however; it looks fairly straightforward! Chris ___ 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: emacs and gconf troubles
On 12/05/10 15:18, Ashish SHUKLA wrote: How're you starting X server ? Through KDM. And with which version are you seeing this behaviour ? You mean: %pkg_info|grep emacs emacs-23.2_4,2 GNU editing macros ? And are you running GNOME, KDE, or any desktop environment ? KDE. I see this if I start emacs from xterm or if I ssh into another box and start emacs from there. The other box have no X server (but I think this does not matter). I should also have mentioned that I mount home via NFS; statd and lockd are running on all machines. bye & Thanks av. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: otrs-2.4.9
On 30.11.2010 21:01, Piotr Byliński wrote: > Hello, > > Is it possible to know when will otrs-3 > be available in freebsd ports ? Committed. -- Sergey Skvortsov mailto: s...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: emacs and gconf troubles
Andrea Venturoli writes: > On 12/05/10 15:18, Ashish SHUKLA wrote: >> How're you starting X server ? > Through KDM. >> And with which version are you seeing this behaviour ? > You mean: > %pkg_info|grep emacs > emacs-23.2_4,2 GNU editing macros > ? I tried that version as well, but I wasn't able to reproduce the error with my setup, which is 'startx' based, with following contents of $HOME/.xinitrc: #v+ #!/bin/sh xrdb ~/.Xdefaults xmodmap ~/.Xmodmap exec dbus-launch --exit-with-session ck-launch-session xmonad 2>$HOME/.xsession-errors #v- >> And are you running GNOME, KDE, or any desktop environment ? > KDE. > I see this if I start emacs from xterm or if I ssh into another box > and start emacs from there. The other box have no X server (but I > think this does not matter). Are you using X11 forwarding in ssh ? Could you please paste the output of 'export' (or whatever command your shell uses to list all environment variables with their values) ? > I should also have mentioned that I mount home via NFS; statd and > lockd are running on all machines. > bye & Thanks > av. Thanks -- Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 freebsd.org!ashish | http://people.freebsd.org/~ashish/ Avoid Success At All Costs !! pgpXHXz5uyQU4.pgp Description: PGP signature
[patch] Re: A few questions about bsd.port.mk
On Thu, Dec 2, 2010 at 5:49 PM, Eitan Adler wrote: > I noticed a line in bsd.port.mk "Kludge for pre-3.0 systems" > > # Kludge for pre-3.0 ystems > MACHINE_ARCH?= i386 > > According to cvs blame asami@ added both lines in revision 1.306 in 1999 > > Furthermore in bsd.port.mk it says ports should test against ARCH and > not MACHINE_ARCH > but bsd.port.subdir.mk uses MACHINE_ARCH on line 209. > > bsd.gnustep.mk has a similar test for MACHINE_ARCH instead of ARCH on > line 136 (r1.1 by dinoex) > > 1) Should the initial line be removed > 2) Should bsd.port.subdir.mk be changed to use ARCH instead? > 3) Should bsd.gnustep.mk be changed to use ARCH instead? Here is a completely untested patch that makes the changes above. http://isis.poly.edu/~eitan/files/remove-2004-hack.patch Comments on both the patch and my questions are appreciated. -- Eitan Adler ___ 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: [patch] Re: A few questions about bsd.port.mk
Eek - wrong link: https://isis.poly.edu/~eitan/files/remove-machine-arch.patch is the patch I meant. > Here is a completely untested patch that makes the changes above. > http://isis.poly.edu/~eitan/files/remove-2004-hack.patch > Comments on both the patch and my questions are appreciated. > > > -- > Eitan Adler > -- Eitan Adler ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD Port: dovecot-2.0.7
Hi, I was wondering why vpopmail support is disabled in this port. I just tested it on 8-STABLE. It compiles and runs just fine, although I did have to comment out the extra arguments in dovecot's example configuration file (auth-vpopmail.conf.ext) because I'm using neither Maildir++ nor quotas: # [cache_key=] # [quota_template=] - %q expands to Maildir++ quota #args = quota_template=quota_rule=*:backend=%q ___ 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"
