Date: Mon, 14 Dec 1998 10:02:08 +0100 (CET) From: Blaz Zupan <blaz@gold.amis.net> To: Nik Clayton <nik@nothing-going-on.demon.co.uk> Cc: Mikael Karpberg <karpen@ocean.campus.luth.se>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/etc Makefile Message-ID: <Pine.BSF.4.05.9812140941110.588-100000@gold.amis.net> In-Reply-To: <19981213224532.34064@nothing-going-on.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Actually, wouldn't even a text file with documentation on what to do help > > out in this situation? > See > <URL:http://www.nothing-going-on.demon.co.uk/FreeBSD/make-world/make-world.html>; Yes, I know about this one (and I was refering to it in my mail). > You'll also find a pointer to it in the "Using 'make world' to rebuild > your system" part of the Handbook. I also know about this one. > That, in conjunction with 'mergemaster' in the ports should be more than > adequate. I've not heard of anyone have problems upgrading /etc using And here is where I disagree. I know from experience, that going to the web while doing a "make world" can be hard. For example, you made some stupid changes to your machine and broke the networking, so you can't go and visit the web, or you don't even have a web browser available. Yes, it happens! My argument is: yes, documentation on the web is great. But no, not everybody can read it every time they do a make world. That's why I would include a simple README file, for which you don't need anything as fancy as a web browser, you only need "more" and off you go reading it. > I don't know how this can be made more obvious. With including a digested version in the repository ;) The one problem with your documentation is, that there's so much of it. I read through it once when I needed it (thanks, it really helped!). But now I know most of it. But it still happens sometimes that my "make world" blows up - not often, I admit, because I do read -current regullary - because I didn't notice some change that would affect it. If I would try to use your documentation to fix that, I'd have to read it through again as a whole, but that takes time. A simple check-list, available right there, in the repository, maybe sorted chronologically, would help much in this situation. (Chronologically because then one could just look up what happened since he last made world and just do-the-right-steps). And a comment to Eivind, who wants to remove -current cvsup access: I rarely contribute to FreeBSD, but I do cvsup. I try to be up-to-date on my home machine and try to find problems, make suggestions and help as much as I can, time permitting. I'm sure there are others like me. Removing cvsup access would really not help much reducing the noise (you would only get a ton of questions every week, asking why they can't cvsup -current), it would only be an annoyance to those, that try to do their best to help. If I don't have time to contribute today, this week, this month or this year, maybe I'll have time to do it tomorrow, next week, next month or next year. But without -current access, I won't even have a chance to try. Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9812140941110.588-100000>