On Oct 5, 2005, at 9:41 AM, Daniel Macks wrote:
On Wed, Oct 05, 2005 at 09:18:12AM -0700, David R. Morrison wrote:
How about if instead we actually try to make it work without the dev
tools? Things were originally designed that way... And particularly
if we ever get the project of more frequent bindists off the ground,
this could be useful.
What packages (.pkg, not fink) are part of the base system install? Do
we get all the /usr/bin BSD commands, or will we continue to have to
have packages like gzip and tar be essential to make sure dpkg can use
those commands (/me notes ?
All of the standard BSD commands are there, if the user has installed
BSD.pkg. I believe that this may have required a custom install at
some point in time, but I think its installed by default now.
Certainly I wouldn't suggest anyone try to use fink without this
being present, and perhaps fink should test for its presence.
As for the case at hand, we could easily make 'make' essential and a
dependency of 'fink'.
Well, binary-only users shouldn't need 'make'; we should try to
design things so that they don't.
If the issue is that fink needs certain things only when not using
bindist, maybe we should have 'selfupdate' give a huge warning iff
those things are not present and user tries to selfupdate using cvs or
rsync.
More than just a warning: I would like to see the cvs and rsync
options as being available only if you have the dev tools installed.
Binary-only users should be using the "point" update method.
-- Dave
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
