Summary: | wget isn't required in the macos profile's system definition. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ed Schouten <edschouten> |
Component: | [OLD] Unspecified | Assignee: | osx porters <osx> |
Status: | VERIFIED FIXED | ||
Severity: | minor | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | PPC | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ed Schouten
2004-07-29 08:26:39 UTC
Err... curl is what's available initially. Pulling in wget shouldn't be required in the profile like it is. What you're after is having portage determine that wget is available, and override the existing fetchcommand/resumecommand... which isn't going to happen w/out a lot of argueing regarding the usefulness of it. Directing this to osx since it's an issue w/ their profile. The situation is: both make.globals and make.conf have the FETCH thing set to curl because that one is installed out of the box. wget is fancier, and the request is to have globals set to wget and .conf set to curl initially, to allow this to be changed more easily later on. I've put wget and nano in the system profile, to make give the system the gentoo feel, and maybe make things easier documentation wise. Ideas, thoughts? If it's not really required, should it even be in system? Many gentoo users don't want the bloat. I think it should be an option (to emerge wget and use it with portage thereafter). Anyone else have thoughts on this? I'll remove wget from the profile. Pieter done. Closing out bugs that've been resolved for a while now... |