Detecting dependencies
Hi, There have been a discussion about finding interdependencies of ports. I have a relatively simple Python script for that. There is a pr ports/160007 to add its early version. Unfortunately, I missed a reply to it, so there is an issue which I have not yet addressed... Since that time, I added reverse dependencies with full ports tree scanning (1 h on my 2.5GHz notebook) and saving the tree (directed graph, actually) to a file, so that rescanning all ports tree is not needed. See http://code.google.com/p/porttree/ If there will be interest, scanning packages interdependencies could also be added. -- Vladimir Chukharev Tampere University of Technology ___ 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"
PowerMath - Your Virtual Mathematics Assistant
PowerMath - Your Virtual Mathematics Assistant Changing the Way People Learn If you are unable to see this page < Click Here > Fall 2011 Computer Animated Lesson Shows : Courses in Arithmetic, Algebra, Geometry, Trigonometry, Pre-Calculus, Calculus, Probability and Statistics covering Middle-School, High-School and University level Mathematics, for Students and Instructors. for less than $0.67 cents per day PowerMath has been featured on among others . . . Exclusion: If you no longer wish to receive email from PowerClassroom Software invoke < delete > Please do NOT reply to this e-mail if you wish to unsubscribe, instead use the instructions above. Any/all information collected from our customers will not be sold, shared, or rented. ___ 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: Thank you (for making the ports less boring).
Quoth Tony Mc on Wednesday, 14 September 2011: > On Tue, 13 Sep 2011 21:27:22 +0200 > Michal Varga wrote: > > > I have no other words beyond that because I can't even seriously > > imagine what those people stating how everything is perfectly fine > > now consider to be a working, modern, 24/7 ready desktop workstation. > > I am interested to know what you regard as a modern 24/7 ready desktop > workstation. Seriously, I would like to know what you think I am > missing by being happy with FreeBSD. I manage to read stuff, write > stuff, print stuff, listen to stuff, watch stuff, backup stuff, archive > stuff, burn CDs and DVDs - what am I missing? I use tcsh > and command-line tools and Emacs and org-mode and LaTeX and claws-mail > and Firefox and Rhythmbox and JPilot to sync with my Palm TX. When > people send me Microsoft Office documents I even use LibreOffice > occasionally. I use XFCE4 as my desktop environment and switch virtual > desktops to focus on different kinds of activity. The computer runs > 24/7 and performs housekeeping tasks overnight and is there again in > the morning when I need to start work. > > I suppose my needs aren't that sophisticated - but I also wonder if > what is missing is truly sophistication or simply different ways of > accomplishing existing tasks. So if you have the time I would genuinely > be interested to learn what a modern desktop machine now needs or > offers. > > Best, > Tony By contrast, I avoid the GUI stuff as much as I can. I use a tiling window manager and almost everything I do, from writing code to listening to music, happens in a terminal window. My editor is vim, and my MUA is mutt. Yet as different as our desktop experiences are, FreeBSD powers them both. One of the reasons I like FreeBSD for the desktop is that I can make it anything I want. With Windows, I have to accept how Windows works -- the ability to customize that experience is extremely limited. -- .O. | Sterling (Chip) Camden | http://camdensoftware.com ..O | sterl...@camdensoftware.com | http://chipsquips.com OOO | 2048R/D6DBAF91 | http://chipstips.com pgpnEL0dBZBje.pgp Description: PGP signature
Re: Thank you (for making the ports less boring).
On Tue, 13 Sep 2011 21:27:22 +0200 Michal Varga wrote: > I have no other words beyond that because I can't even seriously > imagine what those people stating how everything is perfectly fine > now consider to be a working, modern, 24/7 ready desktop workstation. I am interested to know what you regard as a modern 24/7 ready desktop workstation. Seriously, I would like to know what you think I am missing by being happy with FreeBSD. I manage to read stuff, write stuff, print stuff, listen to stuff, watch stuff, backup stuff, archive stuff, burn CDs and DVDs - what am I missing? I use tcsh and command-line tools and Emacs and org-mode and LaTeX and claws-mail and Firefox and Rhythmbox and JPilot to sync with my Palm TX. When people send me Microsoft Office documents I even use LibreOffice occasionally. I use XFCE4 as my desktop environment and switch virtual desktops to focus on different kinds of activity. The computer runs 24/7 and performs housekeeping tasks overnight and is there again in the morning when I need to start work. I suppose my needs aren't that sophisticated - but I also wonder if what is missing is truly sophistication or simply different ways of accomplishing existing tasks. So if you have the time I would genuinely be interested to learn what a modern desktop machine now needs or offers. Best, Tony ___ 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: Thank you (for making the ports less boring).
On Wed, 14 Sep 2011 00:20:13 +0200 Matthias Andree wrote: [...] > I think you mentioned Arch Linux, further suggestions would be Gentoo > Linux (you might like emerge), and further options are Debian > GNU/kFreeBSD and using a FreeBSD base system with pkgsrc (rather than > ports) on top. Came as Gentoo user, abandoned Gentoo because of to many quirks with updating packages (ebuilds). From my perspective, the situation is better here (FreeBSD). Cheers -- Christopher J. Ruwe TZ GMT + 2 pgpzNAteUNkv3.pgp Description: PGP signature
Re: testing PKGNG
Em Qua, 2011-09-14 às 10:43 +0200, Baptiste Daroussin escreveu: > > no pkgng do ont share something penguinist at all :) > > pkgng is just the result of long studies and reflexion about packaging > (studying > what is done elsewhere: apt/dpkg, yum/rpm, pacman, aix, solaris, > netbsd, openbsd > and how to have something that try to take the good ideas from there, > try not to > take the *over engineered* complicated part. And most important try to > do it the > FreeBSD way: which means it should work with the ports tree as-is (and > help > improve it in the future), so we are safe no real penguinism in > pkgng :) I think pkgng will on on his way to the freebsd release (perhaps the 9.x will include it in the base system) but I need a solution now. Even if portmaster, is an excelent software, it could not help me (40 servers, and counting...) each server with about 880 packages that must be in sync The solution pkgng gives me, is what I was looking for, even the software is "alpha"... and sure have some problems, the version I tested (the one is in the servers) is working for me. I even tried to port "pacman, from arch linux", but pkgng is even faster.. Sergio ___ 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"
dbmail 3.0-rc3
The dbmail version 3 final release candidate is available for testing and pre upgrade planning. As this is a release candidate it is not meant for production use. As the current maintainer appears to have gone away I've made a port available at http://p-o.co.uk/dbmail-devel.tar.bz2 for wider FreeBSD testing. There are a number of significant changes including Dependencies, Config, Schema and Server changes. See UPGRADING for details. Any issues with the FreeBSD port please contact me, all other issues please raise an issue with the support tracker at dbmail.org. Alan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: cvs commit: ports/x11/nvidia-driver Makefile distinfo
В Wed, 14 Sep 2011 13:54:02 +0200 Michal Varga пишет: > On Wed, 2011-09-14 at 07:38 -0400, Jerry wrote: > > On Wed, 14 Sep 2011 13:01:50 +0200 > > Alex Dupre articulated: > > > > > Dmitry Marakasov ha scritto: > > > > * Alexey Dokuchaev (da...@freebsd.org) wrote: > > > > > > > >> Log: > > > >> - Update NVidia drivers to their corresponding latest > > > >> versions > > > >> - Apply a workaround to fix the build on recent -CURRENT > > > >> after fget(9) KPI was changed in r224778 (affects the driver > > > >> since version 195.22) > > > > > > > > Just for everyone's information, I've had system freezes with > > > > 280.13, 8.2-RELEASE i386, GeForce 9800 GT. > > > > > > I can confirm the freeze with 8.2 amd64 and a GeForce GTS 450. I > > > had to downgrade to 270.41.19. > > > > I just checked on one of my machines, and it is working correctly. > > > > dmesg | grep -i geforce > > nvidia0: on vgapci0 > > > > This is a FreeBSD-8.2 amd64 machine and the card is not exactly > > "start of the art" either. > > > > I'm using 280.13 since the hour it came out (atm on > 8.2-STABLE i386) for 2D and 3D graphics work, VDPAU video > acceleration, 3D gaming, desktop effects, for about 20 hours a day on > average. > > I have yet to see a single freeze or any other issue. > > m. > > Forgot to add 'G86 [GeForce 8400M GS]' ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: cvs commit: ports/x11/nvidia-driver Makefile distinfo
В Wed, 14 Sep 2011 13:54:02 +0200
Michal Varga пишет:
> I'm using 280.13 since the hour it came out (atm on
> 8.2-STABLE i386) for 2D and 3D graphics work, VDPAU video
> acceleration, 3D gaming, desktop effects, for about 20 hours a day on
> average.
>
> I have yet to see a single freeze or any other issue.
I'm using 280.13 FreeBSD 9.0-BETA2 #0 r225506M amd64.
With patch:
--- ./src/nvidia_subr.c.orig2011-04-14 07:09:57.0 +0300
+++ ./src/nvidia_subr.c 2011-04-14 07:11:11.0 +0300
@@ -252,8 +252,8 @@
sc->BAR_recs[i] = res;
}
-if ((rm_read_registry_dword(sp, NULL, "NVreg",
-"EnableMSI", &enable_msi) == RM_OK) && (enable_msi != 0)) {
+if ((resource_int_value(device_get_name(dev), device_get_unit(dev),
+"msi", &enable_msi) == 0) && (enable_msi != 0)) {
count = pci_msi_count(dev);
if ((count == 1) && (pci_alloc_msi(dev, &count) == 0))
sc->irq_rid = 1;
I use compiz.
Freezing system occurs only when playing flash with option
in /etc/adobe/mms.cfg:
OverrideGPUValidation=true
EnableLinuxHWVideoDecode=1
FullScreenDisable=false
AutoUpdateDisable=true
The mouse pointer may move while and and after a while the system
continues to work on, but the command dmesg there are reports :
Sep 13 18:15:33 nonamehost kernel: NVRM: Xid (:01:00): 8, Channel
0004 Sep 13 18:15:45 nonamehost kernel: NVRM: Xid (:01:00):
8, Channel 0003 Sep 13 18:15:58 nonamehost kernel: NVRM: Xid
(:01:00): 8, Channel 0001 Sep 13 18:16:12 nonamehost kernel:
NVRM: Xid (:01:00): 8, Channel 007e Sep 13 18:17:01
nonamehost kernel: NVRM: Xid (:01:00): 8, Channel 007e
I sent an error message on freebsd-gfx-bugs at nvidia dot com created a
script nvidia-bug-report.sh - in the hope that it will fix ... :D
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: cvs commit: ports/x11/nvidia-driver Makefile distinfo
On Wed, 14 Sep 2011 07:38:13 -0400 Jerry wrote: > On Wed, 14 Sep 2011 13:01:50 +0200 > Alex Dupre articulated: > > > Dmitry Marakasov ha scritto: > > > * Alexey Dokuchaev (da...@freebsd.org) wrote: > > > > > >> Log: > > >> - Update NVidia drivers to their corresponding latest versions > > >> - Apply a workaround to fix the build on recent -CURRENT after > > >> fget(9) KPI was changed in r224778 (affects the driver since > > >> version 195.22) > > > > > > Just for everyone's information, I've had system freezes with > > > 280.13, 8.2-RELEASE i386, GeForce 9800 GT. > > > > I can confirm the freeze with 8.2 amd64 and a GeForce GTS 450. I had > > to downgrade to 270.41.19. > > I just checked on one of my machines, and it is working correctly. > > dmesg | grep -i geforce > nvidia0: on vgapci0 > > This is a FreeBSD-8.2 amd64 machine and the card is not exactly "start > of the art" either. > Hi, GeForce G105M, nvidia-driver-280.13, head amd64 (r225099) works fine for me -- wbr, tiger ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: cvs commit: ports/x11/nvidia-driver Makefile distinfo
On Wed, 2011-09-14 at 07:38 -0400, Jerry wrote: > On Wed, 14 Sep 2011 13:01:50 +0200 > Alex Dupre articulated: > > > Dmitry Marakasov ha scritto: > > > * Alexey Dokuchaev (da...@freebsd.org) wrote: > > > > > >> Log: > > >> - Update NVidia drivers to their corresponding latest versions > > >> - Apply a workaround to fix the build on recent -CURRENT after > > >> fget(9) KPI was changed in r224778 (affects the driver since > > >> version 195.22) > > > > > > Just for everyone's information, I've had system freezes with > > > 280.13, 8.2-RELEASE i386, GeForce 9800 GT. > > > > I can confirm the freeze with 8.2 amd64 and a GeForce GTS 450. I had > > to downgrade to 270.41.19. > > I just checked on one of my machines, and it is working correctly. > > dmesg | grep -i geforce > nvidia0: on vgapci0 > > This is a FreeBSD-8.2 amd64 machine and the card is not exactly "start > of the art" either. > I'm using 280.13 since the hour it came out (atm on 8.2-STABLE i386) for 2D and 3D graphics work, VDPAU video acceleration, 3D gaming, desktop effects, for about 20 hours a day on average. I have yet to see a single freeze or any other issue. m. -- Michal Varga, Stonehenge (Gmail account) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: cvs commit: ports/x11/nvidia-driver Makefile distinfo
On Wed, 14 Sep 2011 13:01:50 +0200 Alex Dupre articulated: > Dmitry Marakasov ha scritto: > > * Alexey Dokuchaev (da...@freebsd.org) wrote: > > > >> Log: > >> - Update NVidia drivers to their corresponding latest versions > >> - Apply a workaround to fix the build on recent -CURRENT after > >> fget(9) KPI was changed in r224778 (affects the driver since > >> version 195.22) > > > > Just for everyone's information, I've had system freezes with > > 280.13, 8.2-RELEASE i386, GeForce 9800 GT. > > I can confirm the freeze with 8.2 amd64 and a GeForce GTS 450. I had > to downgrade to 270.41.19. I just checked on one of my machines, and it is working correctly. dmesg | grep -i geforce nvidia0: on vgapci0 This is a FreeBSD-8.2 amd64 machine and the card is not exactly "start of the art" either. -- Jerry ✌ jerry+po...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ Life sucks, but death doesn't put out at all. Thomas J. Kopp ___ 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: Thank you (for making the ports less boring).
Stephen Montgomery-Smith wrote: > On 09/13/2011 09:11 AM, Oliver Fromme wrote: > > Stephen Montgomery-Smith wrote: > > > particularly nasty thing to do. I get the impression that each > > > committer has his own special way of doing this. For example, I have > > > personally found that a simple grep won't work, because "grep xxx > > > /usr/ports/*/Makefile*" just creates a line too long for the shell to > > > handle. I use a shell construction involving "find" but I wonder how > > > others do the same thing. > > > > cd /usr/ports > > echo */*/Makefile* | xargs grep xxx > > That's amazing. > > It would never have occurred to me that "echo */*/Makefile*" works when > "grep xxx */*/Makefile*". Is that because "echo" is a builtin command > in csh (which is what I use)? I notice "/bin/echo */*/Makefile*" > doesn't work. Yes, exactly. When the shell executes an external command, it uses the execve(2) syscall, which has a limit for the size of the argument list. This is why xargs(1) exists. In the past century this limit was 64 KB, then it was raised to 256 KB when people started measuring RAM in GB. There's a read-only sysctl for that value: $ sysctl kern.argmax kern.argmax: 262144 Built-in commands are not affected by the limit because they run inside the shell process itself, so the execve(2) syscall is not involved. echo(1) is a built-in command in all common shells, so "echo ... | xargs" always works. However, if you type /bin/echo, you force the shell to execute the external command, so the limit applies again. You can also write "for i in */*/Makefile*; do ..." or similar (in /bin/sh) without worrying for limits, for the same reason. > Is this documented somewhere? Good question. It should be mentioned in the shells' man- pages, e.g. csh(1) mentions it in the "LIMITATIONS" section (among other strange limitations specific to csh). Also, the xargs(1) manpage mentions ARG_MAX, and the execve(2) manpage explains that the syscall will fail (errno E2BIG) if "the number of bytes in the new process' argument list is larger than the system-imposed limit". I'm pretty sure that _every_ book on shell scripting will explain the argument list limit, and how to circumvent it. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: cvs commit: ports/x11/nvidia-driver Makefile distinfo
Dmitry Marakasov ha scritto: > * Alexey Dokuchaev (da...@freebsd.org) wrote: > >> Log: >> - Update NVidia drivers to their corresponding latest versions >> - Apply a workaround to fix the build on recent -CURRENT after fget(9) KPI >> was changed in r224778 (affects the driver since version 195.22) > > Just for everyone's information, I've had system freezes with 280.13, > 8.2-RELEASE i386, GeForce 9800 GT. I can confirm the freeze with 8.2 amd64 and a GeForce GTS 450. I had to downgrade to 270.41.19. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: CFT: rt-4.0.2 port
On 14/09/2011 11:37, Matthew Seaman wrote: > This port has dependencies on three perl modules not already ported, so > I've created new ports for those as well. You can download .shar > archives of all four from: > >http://www.infracaninophile.co.uk/articles/rt40.html Ah. Apparently the three additional perl modules were added to the ports on 1st September. I'll update the rt40 shar shortly. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
CFT: rt-4.0.2 port
Dear all, In the spirit of doing stuff rather than arguing about it, I've put together a port of rt-4.0.2. That's Request Tracker, the popular ticketing system from BestPractical.com. rt-3.6.x and rt-3.8.x are already available in ports, but there's too much good stuff in the new version to forego porting that too. This is a port with (not to put too fine a point on it) a pretty convoluted dependency tree, and a lot of alternate choices for how to install it. So, before I send-pr, I'd like to get it some more sanity checking by a wider audience. This port has dependencies on three perl modules not already ported, so I've created new ports for those as well. You can download .shar archives of all four from: http://www.infracaninophile.co.uk/articles/rt40.html Any feedback gratefully received. Cheers, Matthew PS. What's the preference nowadays -- should simple perl module ports be assigned to p...@freebsd.org by default? -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: testing PKGNG
On Tue, Sep 13, 2011 at 11:16:19PM +0200, Michel Talon wrote: > Sergio wrote: > > >I moved all my servers (about 40) to the pkgng (new generation) > >package/port > >system, and I can say that it is amazing... it is not yet finish, and > >have some > >minor "issues", but works very well, and is lightning fast.. > > > >It is almost the same as "pacman" (from Archlinux).. you build a > >"repository" and install packages from that repository. when you > >update the repository, the other servers can do an "upgrade".. > >you do not have to have the ports tree in each server, and > >you build the ports only on the master server > > > >in the master server, there is a full gnome2 (with 842 dependencies) > >that install right on the shelf with only one command: pkg install > >gnome2 > >now I have a full functional server runing gnome, libreoffice, inkscape > >hplip, cups printing, gdm... in about 30 minutes from internet > > I am extremely interested by what you are saying here. Do you mean that > you can find somewhere precompiled packages that you can install in 30mn > or that you use packages compiled on a master server? Of course the > difference is that if you have just one machine in the basement instead > of a server farm, the point of view is not the same ... > > By the way if you mention that pkgng shares something to some penguinist > system, beware it will be villified by some guardians of the orthodoxy > who are quite vocal. Anyways if it is indeed fast it will make a happy > difference with the present pkg-* tools. > > no pkgng do ont share something penguinist at all :) pkgng is just the result of long studies and reflexion about packaging (studying what is done elsewhere: apt/dpkg, yum/rpm, pacman, aix, solaris, netbsd, openbsd and how to have something that try to take the good ideas from there, try not to take the *over engineered* complicated part. And most important try to do it the FreeBSD way: which means it should work with the ports tree as-is (and help improve it in the future), so we are safe no real penguinism in pkgng :) Bapt pgp9UiwxRonJW.pgp Description: PGP signature
Re: Thank you (for making the ports less boring).
## per...@pluto.rain.com (per...@pluto.rain.com): > > I notice "/bin/echo */*/Makefile*" doesn't work. > > The same (builtin echo works, /bin/echo not) happens in /bin/sh, > and in bash. > > > Is this documented somewhere? > > Not that I know of. There is a limit to the length of arguments to the exec()-functions (measured in bytes). It's even in POSIX.1: ARG_MAX, you can query it with "getconf ARG_MAX". When using shell builtins (like echo, instead of the "external" /bin/echo), no exec() happens and the limit does not apply. If I got my history right, this was even in 4.4BSD. Regards, Christoph -- Spare Space. ___ 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: testing PKGNG...
On Mon, Sep 12, 2011 at 10:53:20PM -0300, Sergio de Almeida Lenzi wrote: > Hello, > > I moved all my servers (about 40) to the pkgng (new generation) > package/port > system, and I can say that it is amazing... it is not yet finish, and > have some > minor "issues", but works very well, and is lightning fast.. > > It is almost the same as "pacman" (from Archlinux).. you build a > "repository" and install packages from that repository. when you > update the repository, the other servers can do an "upgrade".. > you do not have to have the ports tree in each server, and > you build the ports only on the master server > > in the master server, there is a full gnome2 (with 842 dependencies) > that install right on the shelf with only one command: pkg install > gnome2 > now I have a full functional server runing gnome, libreoffice, inkscape > hplip, cups printing, gdm... in about 30 minutes from internet > > > Sergio... > Wahou, Thanks for that great feedback :) Finally something interesting on that list... Nice to hear and really happy that pkgng while still be highly experimental works so good on your case. Now that you have become our larger tester, feedback are really welcome: - bug reports, - features resquest, - documentation :D I may recommand you to well test your upgrades before deploying them. Upgrade process has to be refactor because it works but have some rough edges. I use exclusively pkgng on my boxes (only 4 sorry :)) for weeks now without major problem that can't be fixed. We are also interested in the procedures, I mean the way you build the packages and the way you deploy them, I may have some things to point you to that can help you managing your servers using pkgng :) http://wiki.FreeBSD.org/pkgng https://github.com/pkgng/pkgng irc://#pkgng@freenode regards, Bapt pgpYkW8ao8B5L.pgp Description: PGP signature
Re: Thank you (for making the ports less boring).
Stephen Montgomery-Smith wrote: > It would never have occurred to me that "echo */*/Makefile*" > works when "grep xxx */*/Makefile*". Is that because "echo" > is a builtin command in csh (which is what I use)? I don't know, but I can think of no better explanation. > I notice "/bin/echo */*/Makefile*" doesn't work. The same (builtin echo works, /bin/echo not) happens in /bin/sh, and in bash. > Is this documented somewhere? Not that I know of. ___ 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"
Detecting dependencies
Howdy, A couple of recent threads have mentioned clever ways to search for dependencies. One problem ... there aren't any. :) The *only* safe way to make sure you have found all possible references to a dependency is to grep the entire ports tree (grep -r category/portname /usr/ports/*). There are just too many clever things that people do in various files that aren't given conventional names that you will likely miss some references if you don't. Particularly useless (by itself) is using the INDEX to find dependencies because it will miss any optional dependencies that are not enabled by default. It is usually useful to cross-check the outcome of your grep command to make sure that you have captured at least the known on-by-default ones. hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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"
Thank YOU [1] ...
... for helping me set my priorities strait. [2] It used to be fun to be here. I understand that, in general, people want to help. I understand that there can be a lot of useful input from people that actually do nothing or next to nothing in terms of coding, documenting and so on. I understand that perfectly reasonable and intelligent people might differ about various issues. It used to be good being here. What I CAN NOT understand is when people start insulting other people from the community. This is the point where my understanding and sympathy stops. PLEASE take a break. Go back on vacation. Whatever it takes to cool down. Come back in two weeks and think it over. Be polite. At very least be polite. Curb your sarcasm. No one is after *you*. No one wants to sink the FreeBSD ship. The opposite. It used to be fun to be here. It used to be good. NOT ANYMORE. I don't see what you'll gain when the 90% of top very active committers [3] (think gnome, think kde, thing office, think infrastructure, think $little_ports that 3 people use) dread to open freebsd-ports mail folder; when after reading a couple of messages they'd rather go drink something, watch TV, or whatever, instead of doing something for FreeBSD. You disagree with this or that or the other one? Put a team together or be the lone warrior and start DOING something. Be clear, succinct and, again, POLITE when you write about your new project. You can convince the others? You know how to do it better? You don't know how do to it better, but you think you can motive and manage people that do know? You can take all our work, for FREE, under the most permissive license out there. Fork. Do it better; for others; for you; for us; for me. The rest of you, please > ssh freefall.freebsd.org "tail -2 /etc/motd" and keep up the good work. [1] YOU (plural). I shouldn't need to tell you who you are. I won't. You demotivated me more that enough. [3] Just in case you were wondering, it's a real number, not something I came up with. It used to be fun to be here. It used to be good. It USED to be. [2] No, I'm not going away. I put to much work and time in FreeBSD. But, for the foreseeable future, if you need to contact me about my ports, or other work, or anything else, mail me directly; I won't be reading this list. -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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"
