Does the 'fink cleanup --debs' function really work? On my machine, I am
finding that executing that leaves behind many previous versions of software
in /sw/fink/10.6/unstable/main/binary-darwin-x86_64/sci, etc. For example...
[MacPro:main/binary-darwin-x86_64/sci] howarth% ls ccp4*
ccp4-dev_6.1.1-9_darwin-x86_64.deb ccp4-shlibs_6.1.1-9_darwin-x86_64.deb
ccp4_6.1.1-9_darwin-x86_64.deb
ccp4-dev_6.1.13-1_darwin-x86_64.deb ccp4-shlibs_6.1.13-1_darwin-x86_64.deb
ccp4_6.1.13-1_darwin-x86_64.deb
ccp4-dev_6.1.2-1_darwin-x86_64.deb ccp4-shlibs_6.1.2-1_darwin-x86_64.deb
ccp4_6.1.2-1_darwin-x86_64.deb
ccp4-dev_6.1.2-4_darwin-x86_64.deb ccp4-shlibs_6.1.2-4_darwin-x86_64.deb
ccp4_6.1.2-4_darwin-x86_64.deb
ccp4-dev_6.1.3-1_darwin-x86_64.deb ccp4-shlibs_6.1.3-1_darwin-x86_64.deb
ccp4_6.1.3-1_darwin-x86_64.deb
shouldn't fink have removed all previous debs except for the current version
and revision?
Jack
ps The fink wiki claims...
--debs
Delete .deb files (compiled binary package archives) corresponding to versions
of packages that are neither described by a package description (.info) file in
the currently-active trees nor presently installed.
so this doesn't seem to be the expected behavior for fink unstable.
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT data
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users
