Please update x11-toolkits/fltk from 1.1.7 to current version
There's bug affect compiling remotely/in console: Fluid needs X connection to compile Fl_Help_View widgets(http://www.fltk.org/str.php?L1318) Which already fixed in current version 1.1.x-r5989. The version in ports tree is 1.1.7, I wish it could be updated while it affecting a new port's compiling, which I just submitted: http://www.freebsd.org/cgi/query-pr.cgi?pr=118235 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: libfpx-1.2.0.12_1
Hi there! I am sorry to tell you, but i think this link doesnt work :( http://aldan.algebra.com/~mi/fpx.mega-patch.2007-11-01.bz2 Regards, Eleni ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
libgphoto2-2.4.0 - PTPBUG_DELETE_SENDS_EVENT caused hang for Canon IXUS 55 and S3 IS
Recently I noticed that attempting to delete gphotos from my Canon IXUS 55 in gtkam would just hang. After some experimentation, combined with looking at older sources (which did not hang), I tracked the behaviour down to the PTPBUG_DELETE_SENDS_EVENT flags in libgphoto2. I purchased a Canon S3 IS for my parents, and briefly trialled this - noting the same behaviour. In both cases removing the PTPBUG_DELETE_SENDS_EVENT flag in camlibs/ptp2/library.c appeared to fix the issue. I've attached a patch for this. I guess this might be worth a pr, but I wondered if other Canon owners were seeing this? As the subject says, libgphoto2-2.4.0 is the version I'm patching. Cheers Mark ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libgphoto2-2.4.0 - PTPBUG_DELETE_SENDS_EVENT caused hang for Canon IXUS 55 and S3 IS
Mark Kirkwood píše v po 26. 11. 2007 v 09:21 +1300: Recently I noticed that attempting to delete gphotos from my Canon IXUS 55 in gtkam would just hang. After some experimentation, combined with looking at older sources (which did not hang), I tracked the behaviour down to the PTPBUG_DELETE_SENDS_EVENT flags in libgphoto2. I purchased a Canon S3 IS for my parents, and briefly trialled this - noting the same behaviour. In both cases removing the PTPBUG_DELETE_SENDS_EVENT flag in camlibs/ptp2/library.c appeared to fix the issue. I've attached a patch for this. I guess this might be worth a pr, but I wondered if other Canon owners were seeing this? As the subject says, libgphoto2-2.4.0 is the version I'm patching. Hi, have you contacted gphoto authors about this? I'm sure they will be interested fixing this for the next release. -- Pav Lucistnik [EMAIL PROTECTED] [EMAIL PROTECTED] Shop at the Mobius Strip Mall: Always on the same side of the street! signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: ports modifying system setups
Gergely CZUCZY wrote: On Wed, Nov 21, 2007 at 11:43:35PM -0800, Doug Barton wrote: Gergely CZUCZY wrote: echo 'sevice_enable=YES' /etc/rc.conf.local Yes, I think we all know how to go about this manually. The question at hand is whether or not it's possible or desirable to create the possibility of doing it for the user at port install time. If what you're trying to say here is that you don't find such a facility interesting or necessary, thanks for stating your opinion. I said, that this can be done from the Makefile as well, if that OPTIONS of yours is enabled. Seeing as I was gone (really way gone) from the FreeBSD community for a while, but I used to be very closely associated, I felt that it was possible that because I had seen both environments (several other unixes, like Solaris and different Linuxes) and FreeBSD, that before I stopped seeing things as novel, I might be able to point out some differences that might be useful. I've seen a lot of knee-jerk responses to anything new; this group isn't the largest, but they ARE the loudest. I'm not sayiing I'm right, but I AM saying that it's worth some serious consideration. I'm suggesting a number of ideas that just might be worth adding. In this case, what I meant was to change the rules, the commonly accepted methods, for ports to install daemons, to that they directly patch an rc file, not to make some change in bsd.port.mk, but it really wouldn't be all that hard to code up some macro to do this, so perhaps the idea is sound. I'm currenlty going to present something regarding adding a ports screening method, but that's a much harder thing to code. This macro handler, that would be comparatively easy. I see that we need to decide whether to do it or not, but that decision can wait until I have a macro, a diff to gbsd.port.mk coded up, so we don't discuss this twice (you can kill the idea very well then, you['re not going to lose the opportunity). The only things I see to decide NOW are: 1) name of this proposed macro. I like INSTALL_DAEMON_NAME, do you? 2) the name of the file to carry the resulting definitions. It could be /etc/rc.local, I saw that suggested, but I would like to say why I like $(PREFIX)/local/etc/rc.d. I would rather that the dividing line between any and all system stuff and ports stuff be very very firm and clear. I detest the Linux habit of folding /usr/bin and /usr/local/bin together, and I would really want to maintain FreeBSD's current stance on this. Next couple days, I will show you folks a diff about this. We can make the changes on the two items above rather easily then, but you might want to post your feelings now on it. Save the argument over the entire notion until I get a diff ready. I mean, that's the FreeBSD way, that no one gets any sort of prior blanket approval, and I wouldn't change it for the world. Sincerely, Gergely Czuczy mailto: [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Idea about the ports tree included in the release
RW wrote: On Fri, 23 Nov 2007 20:00:59 -0800 Doug Barton [EMAIL PROTECTED] wrote: How hard would it be to include the c[v]sup checkouts file with the tarball, and install it into some standard location? I think that would greatly increase the utility of the tarball, since you could start from there and immediately update to the latest version without having to pull down the whole tree again. c[v]sup doesn't have to pull the whole tree again if it doesn't have a checkout file, it's just a kind of metadata cache that speeds things up and reduces the server load. I think you dramatically misunderstand what I'm suggesting, and why it would be beneficial. Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
[HEADSUP] new package status/statistics uploaded to portsmon.freebsd.org
I've been generating these locally but not uploading them. Now, they are up-to-date. If you are interested in what the state of the packages is on the various architectures, these pages will be of interest. Of particular interest to ports committers is the new page http://portsmon.freebsd.org/checkpackages.html. This shows the status of the packages that go on disc1 and disc2 of the release CDs. When you click on the table header for each buildenv, it will take you to a page that shows the complete package status for that buildenv, including whether packages are marked IGNORE or BROKEN, or simply have errors. For each package in the checkpackages page, you'll need to search the most right-hand column of the status page to find out what package is blocking it, if it's a dependency of something else. The overall comparison amongst buildenvs is at the following: http://portsmon.freebsd.org/chartsandgraphs/package_comparison.html. That's a good start here. Everything else is shown on http://portsmon.freebsd.org/chartsandgraphs/index.html. Note that all this data is as of the last port building run (not whichever one is currently in progress), so certain errors may already have been fixed. The information is all there -- but you may have to do a little bit of detective work with e.g. the individual port pages and the cvsweb links. For instance, amd64-7, i386-7, and sparc64-6 have been unblocked by the most recent commits. However, sparc64-7 is still blocked on x11/gnome2 via the build error in devel/pwlib, which appears to have happened when the threading libraries were switched. (Anyone willing to help track that down?) mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X Can't see my docked monitor - xorg or nvidia?
Doug, Did you ever get this working? I have a simular problem and the workaround I found is to use the nvidia-driver-96xx port instead of the regular nvidia-driver port. I can not remember the exact model of the Dell FP display that I have ( it is at work) but it is the same resolution (1600x1200). On Nov 11, 2007 4:01 PM, Doug Barton [EMAIL PROTECTED] wrote: Thanks for responding, sorry it took so long to get back to you, $REAL_LIFE is in my face lately. All my ports are up to date, including kde 3.5.8, and nvidia-driver 100.14.19. I also tried with and without the -ignoreABI option, no change. I should also point out that I'm using kdm, but I was using it before the upgrade too. Turning kdm off and using startx has no effect (still comes up only on the laptop screen). Any suggestions? The content of /var/log/Xorg.0.log might be useful, http://people.freebsd.org/~dougb/Xorg.0.log There are a couple of interesting sections: (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (WW) OS did not count PCI devices, guessing wildly and (--) NVIDIA(0): Connected display device(s) on Quadro NVS 110M at PCI:1:0:0: (--) NVIDIA(0): DELL 2001FP (CRT-0) (--) NVIDIA(0): LPL (DFP-0) (--) NVIDIA(0): DELL 2001FP (CRT-0): 400.0 MHz maximum pixel clock (--) NVIDIA(0): LPL (DFP-0): 330.0 MHz maximum pixel clock (--) NVIDIA(0): LPL (DFP-0): Internal Dual Link LVDS That all looks right, but (II) NVIDIA(0): Assigned Display Device: DFP-0 That should not be, since the only screen mentioned in xorg.conf (http://people.freebsd.org/~dougb/xorg.conf) is the 2001FP. (WW) NVIDIA(0): No valid modes for 1600x1200; removing. This makes sense because the laptop screen doesn't do that resolution, it's for the 2001FP. but also try and play with xrandr. Xrandr --verbose should tell you what outputs i actually sees, and then you can disable/enable individual outputs and see what happens. Screen 0: minimum 320 x 240, current 1440 x 900, maximum 1440 x 900 default connected 1440x900+0+0 (0x19a) normal (normal) 0mm x 0mm Identifier: 0x199 Timestamp: 811385259 Subpixel: unknown Clones: CRTC: 0 CRTCs: 0 1440x900 (0x19a) 64.8MHz h: width 1440 start0 end0 total 1440 skew0 clock 45.0KHz v: height 900 start0 end0 total 900 clock 50.0Hz ... No mention of the 2001FP at all. Thanks again, Doug If my info will help I'll be glad to gather any needed details tomorrow at work. Let me know if you find a solution and I will try it here too. Thanks, Kelly ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X Can't see my docked monitor - xorg or nvidia?
Kelly Hays wrote: Doug, Did you ever get this working? I have a simular problem and the workaround I found is to use the nvidia-driver-96xx port instead of the regular nvidia-driver port. I can not remember the exact model of the Dell FP display that I have ( it is at work) but it is the same resolution (1600x1200). No, I never got it working with the latest version of the driver. I downgraded the port to 100.14.11 instead of using the 96xx stuff, but the issue with the latest driver remains. Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Package Building in the Large
Doug Barton wrote: Jason C. Wells wrote: Doug Barton wrote: On Mon, 19 Nov 2007, Jason C. Wells wrote: What I am trying to do is to build 30 or so packages including the big ones like X, kde, gnome, plus all of their dependencies on a build host and then use pkg_add on various machines. I have had a variety of difficulties with all of the methods I have used thus far (portmaster, portupgrade, homegrown). What problems did you have with portmaster? Did the backup package creation fail in some way? Not all dependencies had a package built for them. For my list of 31 ports that I actually desired to build there was a dependency list (make all-depends-list) of 758 ports. Of those 758 ports there were 427 packages built. That's disturbing, but I think I know why it happened, see below. I'm more disturbed that this piece of news isn't common knowledge. Those numbers actually understate the problem. Just one commonly required port, one of the browsers like Firefox, alone brings in over 300 dependencies. At least in my own opinion, the largest part of that dependency list is VERY weakly required, mainly a matter of a porter saying to himself I have that port, I like it a lot, everybody should have it and not this port won't run without that port That's my own main motivation behind all that work I'm doing aboout making a ports keyword list, so as to better control the growth of dependency lists. It's no problem at all to show ludicrous examples of overly agressive dependency lists taking the choices of what ports to add out of the hands of the users. As soon as I get the keyword list written (asnd who knows, maybe accepted?), then I intend to push what I see as the second part of this, a tool that looks at what ports are installed, the state of your keyword lists, and a user's personal interests, and make suggestions of what ports a user might find interesting. Sort of a ports-advertiser. This would take the place of overly agressive dependency lists, but not by removing the user from the process, but instead by making that user's selection job easier to make. Such a tool could have a link to a ports installer, even, so as to further ease things, but not to remove the choice from the user, as it's moving towards today. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Idea about the ports tree included in the release
Edwin Groothuis wrote: On Sat, Nov 24, 2007 at 09:39:19AM +0100, Alex Dupre wrote: Doug Barton wrote: In thinking about the guy who posted to -stable about using the tar'ed up version of the ports tree, I had an idea that would make that more useful. How hard would it be to include the c[v]sup checkouts file with the tarball, and install it into some standard location? And why not the portsnap database instead? It seems the default/recommended method today. That would save me 42Mb to download each time :-P But euhm.. it should only be installed on systems which are installed cleanly, not on systems being upgraded via cdrom images. Assuming I understand what you mean, I think one of two things would happen: 1. The drive that the ports tree is on would be reformatted, therefore the new one could be installed, or 2. The drive would not be reformatted, therefore the old (and presumably already functional) ports tree would still be there. Maybe I'm missing something though? Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Package Building in the Large
Chuck Robey wrote: Doug Barton wrote: Jason C. Wells wrote: Doug Barton wrote: On Mon, 19 Nov 2007, Jason C. Wells wrote: What I am trying to do is to build 30 or so packages including the big ones like X, kde, gnome, plus all of their dependencies on a build host and then use pkg_add on various machines. I have had a variety of difficulties with all of the methods I have used thus far (portmaster, portupgrade, homegrown). What problems did you have with portmaster? Did the backup package creation fail in some way? Not all dependencies had a package built for them. For my list of 31 ports that I actually desired to build there was a dependency list (make all-depends-list) of 758 ports. Of those 758 ports there were 427 packages built. That's disturbing, but I think I know why it happened, see below. I'm more disturbed that this piece of news isn't common knowledge. Those numbers actually understate the problem. Just one commonly required port, one of the browsers like Firefox, alone brings in over 300 dependencies. xorg itself brings in 262 dependencies. It is because metaports like xorg and gnome2 have been split into smaller and smaller ports. Thus far, I have never installed a port that I felt brought in unwanted dependencies. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Package Building in the Large
Doug Barton wrote:
On Mon, 19 Nov 2007, Jason C. Wells wrote:
What I am trying to do is to build 30 or so packages including the big
ones like X, kde, gnome, plus all of their dependencies on a build
host and then use pkg_add on various machines. I have had a variety
of difficulties with all of the methods I have used thus far
(portmaster, portupgrade, homegrown).
What I do is this. After building the ports I want (and I admit that I
use vanilla cd the-port; make install clean, I run a little script I
call make-packages. And after I have updated the ports, I run a
program called make-packages-purge to get rid of the old stuff.
I enclose them as attachments.
#!/usr/bin/make -f
PACKAGES?=/usr/home/stephen/packages-7
PKG_DBDIR?=/var/db/pkg
PORTSDIR?=/usr/ports
PKG_LIST!=ls ${PKG_DBDIR}
all:${PKG_LIST:C+(.*)+${PACKAGES}/All/\1.tbz+}
.for target in ${PKG_LIST}
${PACKAGES}/All/${target}.tbz: ${PKG_DBDIR}/${target}/+CONTENTS
@origin=${PORTSDIR}/`sed -n 's/@comment ORIGIN://p' \
${PKG_DBDIR}/${target}/+CONTENTS`; \
if [ $$origin != ${PORTSDIR}/ ] [ -e $$origin ] (! [ -e
$$origin/work ] || [ -e $$origin/work/.install_done* ]); then \
echo creating package ${target}; \
make -C $$origin PACKAGES=${PACKAGES} package-links; \
pkg_create -GjY -b ${target} $@ || (rm -f $@ false); \
fi
.endfor
.BEGIN:
@mkdir -p ${PACKAGES}/All
#!/bin/sh
PACKAGES=/usr/home/stephen/packages-7
DB=/var/db/pkg
for p in `ls $PACKAGES/All | sed s/\.tbz//`; do
if ! [ -e ${DB}/$p ]; then
rm -i $PACKAGES/All/$p.tbz
fi
done
for l in `find $PACKAGES -type l`; do
if ! stat -q -L $l /dev/null; then
rm -f $l
fi
done
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Idea about the ports tree included in the release
On Sun, Nov 25, 2007 at 06:26:09PM -0800, Doug Barton wrote: Edwin Groothuis wrote: On Sat, Nov 24, 2007 at 09:39:19AM +0100, Alex Dupre wrote: Doug Barton wrote: In thinking about the guy who posted to -stable about using the tar'ed up version of the ports tree, I had an idea that would make that more useful. How hard would it be to include the c[v]sup checkouts file with the tarball, and install it into some standard location? And why not the portsnap database instead? It seems the default/recommended method today. That would save me 42Mb to download each time :-P But euhm.. it should only be installed on systems which are installed cleanly, not on systems being upgraded via cdrom images. Assuming I understand what you mean, I think one of two things would happen: Oh wait. The cvsup checkouts file is probably a small (set of) file(s) with some revision information, while the portsnap file is a huge chunk of data with a copy of the ports tree. Edwin -- Edwin Groothuis |Personal website: http://www.mavetju.org [EMAIL PROTECTED]| Weblog: http://www.mavetju.org/weblog/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Idea about the ports tree included in the release
Edwin Groothuis wrote: On Sun, Nov 25, 2007 at 06:26:09PM -0800, Doug Barton wrote: Edwin Groothuis wrote: On Sat, Nov 24, 2007 at 09:39:19AM +0100, Alex Dupre wrote: Doug Barton wrote: In thinking about the guy who posted to -stable about using the tar'ed up version of the ports tree, I had an idea that would make that more useful. How hard would it be to include the c[v]sup checkouts file with the tarball, and install it into some standard location? And why not the portsnap database instead? It seems the default/recommended method today. That would save me 42Mb to download each time :-P But euhm.. it should only be installed on systems which are installed cleanly, not on systems being upgraded via cdrom images. Assuming I understand what you mean, I think one of two things would happen: Oh wait. The cvsup checkouts file is probably a small (set of) file(s) with some revision information, Right, it's a single file whose format is: F 5 1196039185 D ports V ports/.cvsignore,v 3#1e71#110#11782530584#11204#root5#wheel3#4441#0 V ports/CHANGES,v 3#1e71#110#11902805645#937964#root5#wheel3#4441#0 V ports/COPYRIGHT,v 3#1e71#110#11782530594#24604#root5#wheel3#4441#0 V ports/GIDs,v 3#1e71#110#11891345385#141814#root5#wheel3#4441#0 V ports/KNOBS,v 3#1e71#110#11888033805#104554#root5#wheel3#4441#0 V ports/LEGAL,v 3#1e71#110#11934328226#2750624#root5#wheel3#4441#0 V ports/MOVED,v 3#1e71#110#11941329996#7698754#root5#wheel3#4441#0 V ports/Makefile,v 3#1e71#110#11908713865#603194#root5#wheel3#4441#0 D ports/Mk ... Mine is about 19M, but I leave out the language-specific parts of the tree. Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Submitting a new port if send-pr is broken
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Due to a ISP firewall it is not possible for me to send/recv mail how do I submit a new port since send-pr requires email? - -- Aryeh M. Friedman Developer, not business, friendly http://www.flosoft-systems.com -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHSld/J9+1V27SttsRAsFJAJ928L/E/JnA0zOHrp/2kc4u7fxNHACfbXog zIBUl4eyOoYjFg/ut5wNNwU= =kpcW -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Submitting a new port if send-pr is broken
On Mon, Nov 26, 2007 at 12:19:59AM -0500, Aryeh M. Friedman wrote: Due to a ISP firewall it is not possible for me to send/recv mail how do I submit a new port since send-pr requires email? If your ISP filters outbound TCP port 25, then it means they're probably doing so to stop/curb spam or trojans that proliferate through SMTP. They likely leave TCP port 587 open to the world (but there's no guarantee of that either). Every ISP I've seen who does the above outbound filtering does so while providing their own SMTP server available for customer use -- and provides a firewall hole for communicating with their own SMTP servers on TCP port 25. If your ISP filters outbound port 25 and doesn't offer you an SMTP server of their own for use, then that's truly bizarre and you should discuss it with your ISP. You should be able to set up a local mailer/MTA (sendmail, postfix, etc.) and tell it to use your ISP's mail server on TCP port 25, and it all should just magically work unless they require SMTP AUTH (not many do from what I've seen; they base authentication on the source IP of customers). sendmail refers to this feature as SMART_HOST, while postfix refers to it as a transport destination (see transport(5)). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Submitting a new port if send-pr is broken
Hi Aryeh! Due to a ISP firewall it is not possible for me to send/recv mail how do I submit a new port since send-pr requires email? If you have a web browser, you can submit it via FreeBSD's website: http://www.freebsd.org/support/bugreports.html The link is Submit a Problem Report. Chris - -- Aryeh M. Friedman Developer, not business, friendly http://www.flosoft-systems.com -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHSld/J9+1V27SttsRAsFJAJ928L/E/JnA0zOHrp/2kc4u7fxNHACfbXog zIBUl4eyOoYjFg/ut5wNNwU= =kpcW -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports- [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Idea about the ports tree included in the release
Edwin Groothuis wrote: That would save me 42Mb to download each time :-P Oh wait. The cvsup checkouts file is probably a small (set of) file(s) with some revision information, while the portsnap file is a huge chunk of data with a copy of the ports tree. Well, even better: instead of the ports tree tarball (+ cvsup files) we could have *only* the portsnap database on the CD, and let portsnap do the extract work at install time. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Submitting a new port if send-pr is broken
On Mon, November 26, 2007 7:01 am, Chris Haulmark wrote: Hi Aryeh! Due to a ISP firewall it is not possible for me to send/recv mail how do I submit a new port since send-pr requires email? If you have a web browser, you can submit it via FreeBSD's website: http://www.freebsd.org/support/bugreports.html The link is Submit a Problem Report. Chris Indeed, that is the online version, be sure to mark the correct category etc though (Aryeh did that wrong when submitting the bug). -- /\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ ASCII Ribbon Campaign | Against HTML Mail and News ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
