On Fri, 2002-07-05 at 16:24, Sheldon Hearn wrote:
> On (2002/07/05 05:22), Terry Lambert wrote:
> > > This would not fit in with the rest of the world target, which doesn't
> > > clean out stale headers, stale libraries or stale binaries.
> > > Special-casing certain things will surprise people.
> > 
> > Headers and libraries arguably should be removed, so as to avoid
> > errors; not ports headers or libraries -- which aren't in the
> > installation target paths in the first place -- but things like
> > deprecated system headers, etc..
> You and Paul are both pretty "out there" if you think -current users
> will graciously accept a new world order in which ports linked
> dymanically against system libraries won't work between a system upgrade
> and the next port reinstall.

I'm reluctant to suggest something that scares away -current developers,
since I don't think enough people are really working on -current these
days. However, if you are developing FreeBSD then you do need to make
sure you're running -current and not -cruft.

The old mantra of "-current is for developers" still holds and if the
development environment becomes ineffective because people are relying
on current as a work environment then maybe we should tighten the
development environment so it's more suited to those people who are
actually working on FreeBSD itself.

On my -current box I usually rebuild ports quite regularly anyway
because ports get updated pretty frequently.

The only real issue with backwards compatibility is the libraries,
there's nothing else that should severely impact existing installations.
Libraries can easily be dealt with by just moving them to a compat dir.

> If you want to clean out crap left behind by `make world', just do this:
> make world
> rm -r /usr/include            # Make world really should overwrite
> make installincludes          # header files!
> find /bin /sbin /usr/bin /usr/sbin /usr/lib /usr/libexec /usr/share \
>      -type f -mtime +1 -delete

That is precisely what I do periodically (along those lines anyway), and
it is often the case that when I do so I find that I've been running
-cruft and not -current at all.

Paul Richards                    |
FreeBSD Services Ltd             | Order 4.6 on DVD today!
http://www.freebsd-services.com  |

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to