RE: I think I understand how I stay STABLE now, without a lot of hassel! correct me if I'm wrong.
This is what I use now. given to me by the poster... Jim levie. It's excellent. === >From: "Jim Levie" <[EMAIL PROTECTED]> >Subject: Re: need cvsupfile conf for 4 to 4.2 Newbie to cvsup... >Date: Sunday, 4 February 2001 4:21 AM >In article , "Merlin" ><[EMAIL PROTECTED]> wrote: > I have the Kernel Developer+User Stable 4.0 installed (no X11), and am > trying to figure out what to put in the cvsup file to update it to 4.2 > Stable. Then there is a set of instructions like make world I > believe. One thing at a time, so if anyone can help me out with a > suitable conf file, and any instructions etc... to grab the updated > stuff to get to > 4.2, I'd sure be grateful. > > > I've read the spots off the Handbook and everyting else, but the more I > read the more confusing it gets It may not be the most ideal, but I have the following in my supfile: kept in the directory, /usr/local/etc/cvsup ... #*default host=cvsup6.FreeBSD.org *default host=cvsup3.FreeBSD.org *default base=/usr/local/etc/cvsupfile *default prefix=/usr *default release=cvs *default tag=RELENG_4 *default delete use-rel-suffix # Don't use compress on a T1 or faster #*default compress ## Get all Sources # src-all src-crypto src-secure *default tag=. ## Get all Ports # ports-all ## Get the Documentation # doc-all >From where I am I seems to get the best responce from cvsup3, but sometimes it's too busy and I use cvsup6. With both listed in the supfile I just comment out one and enable the other. Also I'm not sure if src-crypto and/or src-secure is needed any more or not. If they aren't necessary their presence doesn't seem to cause any problems. One other thing that I do is to have a refuse file containing: ports/chinese ports/french ports/german ports/hebrew ports/japanese ports/korean ports/russian ports/vietnamese doc/de* doc/es* doc/fr* doc/ja* doc/nl* doc/ru* doc/zh* So that I only get the EN stuff. That reduces the disk useage slightly and correspondingly cuts the time required to cvsup. I keep my cvsup and release file in /usr/sup and run the cvsup with "cvsup /usr/sup/supfile". My /etc/make.conf looks like: USA_RESIDENT=YES CFLAGS= -O -pipe NOPROFILE= true NOGAMES=true# do not build games (games/ subdir) I don't know if USA_RESIDENT does anything any more or not now that the export restrictions on the crypto stuff have been lifted. It's there, everything works, and I'm not inclined to take it out until I see confirmation that it isn't needed. Once you have everything cvsup'd, you use what you've gotten by: # cd /usr/src # make buildworld # make installworld # make buildkernel KERNEL=MY_KERNEL # make installkernel KERNEL=MY_KERNEL If you haven't built a custom kernel on your current installation you can replace MY_KERNEL with GENERIC. If you have a custom kernel config, check to make sure that what you have in your kernel config file is still valid by looking at GENERIC and/or LINT. The last step is to merge in the new /etc stuff and that is most easily done with mergemaster. It will remind you to re-make the /dev stuff and don't forget to do so. -- The instructions said to use Windows 98 or better, so I installed FreeBSD. . cheers Robert > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Cliff Sarginson > Sent: Thursday, 8 February 2001 10:35 PM > To: [EMAIL PROTECTED]; FreeBSD > Subject: Re: I think I understand how I stay STABLE now, without a lot > of hassel! correct me if I'm wrong. > > > > On Thu, Feb 08, 2001 at 04:35:00PM +1000, Robert wrote: > > > What it does mean is that even if one does a cvsup on a > weekly basis say, > > > then the _sources_ are always up to date, and IF one then > needs to do an > > > update/upgrade/kernel build whatever, then one is always > using the latest > > > sources. Now THAT makes sense. So I can go ahead an set up a > cron job, that > > > simply calls the cvsup/supfile say once a week. > > Can you give this dummy (I mean me!) the command line for that.. > I find myself in a lot of confusion about this.. *sigh* > > Cliff > > > Edit /etc/weekly.local and you don't need setup cronjob. > > > > -- > > Igor Robul, Unix System Administrator & Programmer @ sanatorium > "Raduga", > > Sochi, Russia > > http://www.brainbench.com/transcript.jsp?pid=304744 > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-stable" in the body of the message > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Problem with make buildworld on a 3.3RC box
Hi, I am trying to upgrade a machine running 3.3RC to 4.2 Stable. I have tried going to 4.1 RELEASE but make buildworld breaks. I then tried to go to 3 STABLE and get the following error from make buildworld cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 isofs/cd9660/*.h /usr/obj/usr/src/tmp/usr/include/isofs/cd9660 cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 ufs/ffs/*.h /usr/obj/usr/src/tmp/usr/include/ufs/ffs install: ufs/ffs/softdep.h: No such file or directory *** Error code 71 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Is there a specific release I should be supping to? --- Gareth Hopkins To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: FW: maestro3 driver broken?
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 08, 2001 10:29 AM > To: [EMAIL PROTECTED] > Subject: maestro3 driver broken? > > I had no luck compiling a recently-committed driver for > maestro3 sounds cards. The system is 4.2-STABLE, source > cvsup'ed on Feb 7, 2001.Running 'make depend; make' > in /usr/src/sys/modules/sound/driver/maestro3 > produces the output attached below. > > I have emailed to Darrell Anderson <[EMAIL PROTECTED]>, > who seems to have written this driver, but just want to confirm > that I am not doing something wrong. Has anyone else run > into the same problem? I could compile the driver > before I did an upgrade (I believe my old sources were from > Jan 15, 2001, but I am not sure). 4.2-STABLE recently had the kobj changes from 5.0-CURRENT backported. I am moving to Scott Long's 5.0-CURRENT version, which should work in the STABLE now: http://people.freebsd.org/~scottl/maestro3/ That said, it doesn't work yet. It compiles cleanly and the module loads, but the attach fails. The driver's m3_pci_attach() calls pcm_addchan(), which in turn calls chn_init(). Then chn_init() calls CHANNEL_INIT(), but it doesn't invoke the driver's m3_pchan_init() as it should. The sound buf is never allocated, so chn_init() returns ENOMEM. I haven't had time to play with it much yet. The driver works in CURRENT; is there something different in the new method/class pcm framework between CURRENT and STABLE? -Darrell -- Department of Computer Science, Duke University, Durham, NC 27708-0129 Darrell Anderson, anderson -at- cs.duke.edu, http://www.cs.duke.edu/~anderson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: maestro3 driver broken?
On Thu, Feb 08, 2001 at 10:49:15AM -0700, Long, Scott wrote: > Ummm the maestro3 driver isn't in -stable yet. Do you mean that you > cvsup'ed -stable on Feb 7, built world, then grabbed the maestro3 driver > sources from Darrell's webpage? In that case, yes things are broken. The Ah, that's right. I thought I saw maestro3.c in a log from cvsup, but now that I looked through it again, I understood this was only my wishful thinking :-) > kobj bits for newpcm were MFC'd recently, causing the -stable version of the > driver to no longer compile. We had hoped that the -current version of the > driver would 'just work' for the new -stable, but that is apparently not the > case. Top men are working on it =-> Until then, you can back down to an > older -stable, or upgrade to -current. > > Scott > > Scott, thank you for the info. -- Vladimir To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
re: lc_time=c, buildworld error
My bad. "Duh". chmod +x /bin/sh -Chris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
buildworld error, LC_TIME=c date
[root@ns1] [/usr/src]# cd /usr/src [root@ns1] [/usr/src]# make buildworld "/usr/src/Makefile", line 106: warning: "LC_TIME=C date" returned non-zero status /bin/sh:Permission denied *** Error code 1 Stop in /usr/src. wtf? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Ports updating... Good ways?
What about extending "make" so that it is possible to do the following: $ cd /usr/ports/foo/bar $ make update "make" would then automatically deal with updating dependencies for that specific port, remove the old version and build the new one. I know this thread is mostly about updating all your ports at once, but this seems to be a good start. Using "make" in such a way ties in nicely with the current use of the ports system in my opinion. -Brian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
maestro3 driver broken?
I had no luck compiling a recently-committed driver for maestro3 sounds cards. The system is 4.2-STABLE, source cvsup'ed on Feb 7, 2001.Running 'make depend; make' in /usr/src/sys/modules/sound/driver/maestro3 produces the output attached below. I have emailed to Darrell Anderson <[EMAIL PROTECTED]>, who seems to have written this driver, but just want to confirm that I am not doing something wrong. Has anyone else run into the same problem? I could compile the driver before I did an upgrade (I believe my old sources were from Jan 15, 2001, but I am not sure). Vladimir Warning: Object directory not changed from original /usr/src/sys/modules/sound/driver/maestro3 cc -O -pipe -Wall -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -mpreferred-stack-boundary=2 -c /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:77: warning: `AC97_CREATE' redefined @/dev/sound/pcm/ac97.h:78: warning: this is the location of the previous definition /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:85: warning: `KOBJMETHOD' redefined @/sys/kobj.h:94: warning: this is the location of the previous definition /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:86: warning: `AC97_DECLARE' redefined @/dev/sound/pcm/ac97.h:77: warning: this is the location of the previous definition /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:110: warning: `CHANNEL_DECLARE' redefined @/dev/sound/pcm/channel.h:102: warning: this is the location of the previous definition /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:84: conflicting types for `kobj_method_t' @/sys/kobj.h:37: previous declaration of `kobj_method_t' /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:84: warning: redundant redeclaration of `kobj_method_t' in same scope @/sys/kobj.h:37: warning: previous declaration of `kobj_method_t' /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:243: warning: initialization from incompatible pointer type /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:243: warning: initialization makes integer from pointer without a cast /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:243: warning: initialization makes integer from pointer without a cast /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:243: warning: initialization makes integer from pointer without a cast /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:243: warning: initialization makes integer from pointer without a cast /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:243: warning: initialization makes integer from pointer without a cast /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:243: warning: initialization makes integer from pointer without a cast /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:243: warning: initialization makes integer from pointer without a cast /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:243: warning: missing braces around initializer /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:243: warning: (near initialization for `M3_pch_class.buffer') /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:265: warning: initialization from incompatible pointer type /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:265: warning: initialization makes integer from pointer without a cast /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:265: warning: initialization makes integer from pointer without a cast /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:265: warning: initialization makes integer from pointer without a cast /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:265: warning: initialization makes integer from pointer without a cast /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:265: warning: initialization makes integer from pointer without a cast /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:265: warning: initialization makes integer from pointer without a cast /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pci/maestro3.c:265: warning: initialization makes integer from pointer without a cast /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sound/pc
Re: /root permissions after installworld
Andrey Lakhno wrote: > Hi ! > > Why "make installworld" changes /root permissions to 755 ? > It is insecure to have /root directory world readable. Look at /etc/mtree/BSD.root.dist. Perhaps we could change the default... Someone ? Maxime -- Don't be fooled by cheap finnish imitations ; BSD is the One True Code Key fingerprint = F9B6 1D5A 4963 331C 88FC CA6A AB50 1EF2 8CBE 99D6 Public Key : http://www.epita.fr/~henrio_m/ PGP signature
RE: maestro3 driver broken?
Ummm the maestro3 driver isn't in -stable yet. Do you mean that you cvsup'ed -stable on Feb 7, built world, then grabbed the maestro3 driver sources from Darrell's webpage? In that case, yes things are broken. The kobj bits for newpcm were MFC'd recently, causing the -stable version of the driver to no longer compile. We had hoped that the -current version of the driver would 'just work' for the new -stable, but that is apparently not the case. Top men are working on it =-> Until then, you can back down to an older -stable, or upgrade to -current. Scott > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 08, 2001 10:29 AM > To: [EMAIL PROTECTED] > Subject: maestro3 driver broken? > > > I had no luck compiling a recently-committed driver for > maestro3 sounds cards. The system is 4.2-STABLE, source > cvsup'ed on Feb 7, 2001.Running 'make depend; make' > in /usr/src/sys/modules/sound/driver/maestro3 > produces the output attached below. > > I have emailed to Darrell Anderson <[EMAIL PROTECTED]>, > who seems to have written this driver, but just want to confirm > that I am not doing something wrong. Has anyone else run > into the same problem? I could compile the driver > before I did an upgrade (I believe my old sources were from > Jan 15, 2001, but I am not sure). > > Vladimir > > > > > > > Warning: Object directory not changed from original > /usr/src/sys/modules/sound/driver/maestro3 > cc -O -pipe -Wall -D_KERNEL -Wall -Wredundant-decls > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Winline -Wcast-qual -fformat-extensions > -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include > -mpreferred-stack-boundary=2 -c > /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sou > nd/pci/maestro3.c > /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sou > nd/pci/maestro3.c:77: warning: `AC97_CREATE' redefined > @/dev/sound/pcm/ac97.h:78: warning: this is the location of > the previous definition > /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sou > nd/pci/maestro3.c:85: warning: `KOBJMETHOD' redefined > @/sys/kobj.h:94: warning: this is the location of the > previous definition > /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sou > nd/pci/maestro3.c:86: warning: `AC97_DECLARE' redefined > @/dev/sound/pcm/ac97.h:77: warning: this is the location of > the previous definition > /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sou > nd/pci/maestro3.c:110: warning: `CHANNEL_DECLARE' redefined > @/dev/sound/pcm/channel.h:102: warning: this is the location > of the previous definition > /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sou > nd/pci/maestro3.c:84: conflicting types for `kobj_method_t' > @/sys/kobj.h:37: previous declaration of `kobj_method_t' > /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sou > nd/pci/maestro3.c:84: warning: redundant redeclaration of > `kobj_method_t' in same scope > @/sys/kobj.h:37: warning: previous declaration of `kobj_method_t' > /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sou > nd/pci/maestro3.c:243: warning: initialization from > incompatible pointer type > /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sou > nd/pci/maestro3.c:243: warning: initialization makes integer > from pointer without a cast > /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sou > nd/pci/maestro3.c:243: warning: initialization makes integer > from pointer without a cast > /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sou > nd/pci/maestro3.c:243: warning: initialization makes integer > from pointer without a cast > /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sou > nd/pci/maestro3.c:243: warning: initialization makes integer > from pointer without a cast > /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sou > nd/pci/maestro3.c:243: warning: initialization makes integer > from pointer without a cast > /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sou > nd/pci/maestro3.c:243: warning: initialization makes integer > from pointer without a cast > /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sou > nd/pci/maestro3.c:243: warning: initialization makes integer > from pointer without a cast > /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sou > nd/pci/maestro3.c:243: warning: missing braces around initializer > /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sou > nd/pci/maestro3.c:243: warning: (near initialization for > `M3_pch_class.buffer') > /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sou > nd/pci/maestro3.c:265: warning: initialization from > incompatible pointer type > /usr/src/sys/modules/sound/driver/maestro3/../../../../dev/sou > nd/pci/maestro3.c:265: warning: initialization makes integer > from pointer without a cast > /usr/src/sys/modules/s
Re: Ports updating... Good ways?
An important note I forgot to mention: pkg_upgrade does not deal well with inconsistent installed packages. Make sure your packages are neat and tidy before you start using it. What does that mean? Mainly, make sure you don't have multiple installed versions of the same version of a piece of software. Having ncftp2 and ncftp3 both installed is fine, but having gtk-1.2.8, gtk-1.2.7, and gtk-1.2.6 installed is not a terribly good idea. I'll try to put a "cleanup" mode in one of these days, but it's rather nasty, since basically you have to: pkg_delete all of the versions (including the most recent), pkg_delete all of the programs that depended on older versions, reinstall/rebuild the most recent version, then rebuild the dependent packages. Whee. --David Bushong P.S. Screwed up my .muttrc earlier, so I'm "Timus" On Wed, Feb 07, 2001 at 10:41:18PM -0800, David Bushong wrote: > pkg_version -c, while better than nothing, has quite a few problems, most > significant of which is dependency ordering (making sure that a library that, > say, "xv" depends on gets upgraded before "xv" itself. > > I've been working on a decent upgrade script for the past few months, and now > seems as good a time as any to have people try it out. > > It's called "pkg_upgrade", and you can get it off of: > http://bushong.net/dave/sw/ > > Requirements: > > * At minimum, the INDEX file from the ports tree; better yet is an actual > ports tree (/usr/ports) > * The perl LWP modules (install /usr/ports/www/p5-libwww if you don't have it) > > Features: > > * will usage existing packages if they exist, and optionally build them if > they don't; great for an NFS mounted ports/packages directory > * will try to fetch packages before building > * handles dependencies correctly > * handles the "disappearing library file" problem (new version of lib package > doesn't provide lib that another installed package needs) > * other stuff i can't remember > > Usage is "pkg_upgrade -h" > > For a summary of what it _would_ do, were you to let it, try: > > pkg_upgrade -al > > Comments/feedback/code/replacement better package system for FreeBSD ;) > welcome. > > --David Bushong > > On Wed, Feb 07, 2001 at 10:18:14PM -0800, Mike Harding wrote: > > > > pkg_version -c | sh > > > > often works but you will probably want to spool it to a file. > > > > - Mike H. > > > >Date: Thu, 08 Feb 2001 13:48:07 +1100 > >From: Kal Torak <[EMAIL PROTECTED]> > >X-Accept-Language: en > >Content-Type: text/plain; charset=us-ascii > >Sender: [EMAIL PROTECTED] > >X-Loop: FreeBSD.ORG > >Precedence: bulk > > > >Hiyas, > > > >Just wanted to see if anyone has some good ways of updating installed > >ports... > > > >It would be good if you could update your installed ports as easily > >as the base system, like some sort of script that worked out all the > >dependencies and updated everything :) > > > >So anyone have a better way than slowly doing it by hand? > > > >Cheers! > >Kal. > > > > > >To Unsubscribe: send mail to [EMAIL PROTECTED] > >with "unsubscribe freebsd-stable" in the body of the message > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
/root permissions after installworld
Hi ! Why "make installworld" changes /root permissions to 755 ? It is insecure to have /root directory world readable. -- Best regards, Andrey To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Ports updating... Good ways?
[moved to -ports] If memory serves me right, Mike Harding wrote: > > Well, just to defend myself... > > I find that pkg_version -c is a useful tool for helping me do > upgrades. I do put the result in a file and do the appropriate thing. ^^^ That was my point. You do *not* want to blindly execute the output of "pkg_version -c". I'm about --><-- this far away from crippling the output of "pkg_version -c" so that it can't be run without editing. People don't realize how dangerous this is; like it can actually render a system unusable. (I know, it happened to a good friend of mine.) > I do agree that something better is needed - one issue is the way that > the ports system tracks dependencies. If the dependency was tracked > in the dependent port rather than the other way around (in other > words, the ports notes that it needs the library rather than the > library noting that it is needed by another port) then the whole > upgrade issue would be simpler as you could actually make multiple > scans over the dependencies until everything was in order. Right now > the dependency information is 'lost' if you ugrade a library. Yeah. I posted a brain-dump of what I think is needed to -ports sometime earlier this week or last week. It's actually not that hard now that we have the "port origin" information for installed ports. The hard part is dealing with all the edge cases. I think that it would be a great project for someone to hack on bsd.port.mk to create a "make upgrade" target. But it has to be extremely conservative in the face of pathologies. > Also, > say, upgrading X with the current system will cause huge amounts of > things to be rebuilt - these ports depend on X but not the version. I think that XFree86 is handled as a special case, but your point is well-taken. Bruce. PGP signature
