[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: X4F sources
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: X4F sources
- From: Jacob Meuser <jakemsr_(_at_)_jakemsr_(_dot_)_com>
- Date: Tue, 19 Oct 2004 19:07:58 -0700
- Mail-followup-to: misc_(_at_)_openbsd_(_dot_)_org
On Wed, Oct 20, 2004 at 03:10:49AM +0200, q# wrote:
> On Tue, Oct 19, 2004 at 05:31:36PM -0700, Jacob Meuser wrote:
> > On Wed, Oct 20, 2004 at 01:29:45AM +0200, q# wrote:
> > > On Tue, Oct 19, 2004 at 02:19:32PM -0700, Geoff White wrote:
> > > > Forgive me if I'm dense, but I've looked through the FAQ and even though it
> > > > tells me how to build X4F from sources, it doesn't give any indication
> > > [...]
> > >
> > > When I rebuild XF4 man release(8) help me a lot, but when I create
> > > $RELEASEDIR I'm stuck howto put this on the box. I simply unpacked this
> > > with `tar -xzpf x...tgz -C /' but don't know how to clean old libs from
> > > pevious-XF4 :/
> > shouldn't really be necessary, but you can touch(1) a file before
> > starting a build (or use touch -t), and then use
> > find -type f ! -newer time-stamp.txt | xargs rm
> > this should only be used in directories where all the files are
> > rebuilt. you wouldn't want to accidently remove all your include
> > or share directories.
> Sounds good. I look at install_files() from miniroot, instalation there
> is only `tar zxhpf - -C /mnt', but what about needless-stuff. In middle
> 3.5 - 3.6 there was libm bump. Old lib was libm.so.1.0 and new is
> libm.so.2.0. If I rebuild system and know time-stamp everything is okey,
> but when I want to upgrade obsd from CD, there will be a little mess, or
> not? Old files/name will gone?
there will be old files. they should be harmless (or maybe needed by
third party software).
> You said "shouldn't really be necessary", but how OpenBSD contrive with
> such situation?
in the case of shared libs, probably the sources for ld and ld.so
would have some clues.