[MacPorts] #38180: Request for port: file_cmds
#38180: Request for port: file_cmds ---------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: file_cmds ---------------------+-------------------------------- MacPorts already has portfiles for the bootstrap_cmds and developer_cmds packages from opensource.apple.com, and so, in the interest of working towards the goal of MacPorts being entirely self-hosting one day, I'd like to request that the [http://www.opensource.apple.com/source/file_cmds/file_cmds-212.1/ file_cmds] from opensource.apple.com be added to MacPorts, too. I'm cc-ing mfeiri because he's the maintainer for bootstrap_cmds and developer_cmds. -- Ticket URL: <https://trac.macports.org/ticket/38180> MacPorts <http://www.macports.org/> Ports system for Mac OS
#38180: Request for port: file_cmds ------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: file_cmds | ------------------------+-------------------------------- Comment (by ryandesign@…): Looks like file_cmds provides some very basic commands, like rm and chown. Why would we need a port for those — what OS do we think we might be running on that wouldn't have these basic utilities? -- Ticket URL: <https://trac.macports.org/ticket/38180#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#38180: Request for port: file_cmds ------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: file_cmds | ------------------------+-------------------------------- Comment (by egall@…): Replying to [comment:1 ryandesign@…]:
Looks like file_cmds provides some very basic commands, like `rm` and `chown`. Why would we need a port for those — what OS do we think we might be running on that wouldn't have these basic utilities?
It wouldn't have to be all of them; it's mostly just for `pax` and `mtree`. -- Ticket URL: <https://trac.macports.org/ticket/38180#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#38180: Request for port: file_cmds ------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: file_cmds | ------------------------+-------------------------------- Changes (by mfeiri@…): * cc: mfeiri@… (removed) Comment: I have no objections against such a port. But I also dont see the purpose. The reason for creating the bootstrap_cmds and developer_cmds ports was to facilitate building xnu-headers and friends. The tools provided by bootstrap_cmds and developer_cmds are not included in the base OS. I am not sure who/what would benefit from a port of file_cmds. -- Ticket URL: <https://trac.macports.org/ticket/38180#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts