Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#18718 - [bin86] [ed] remove from base-devel group
Attached to Project:
Arch Linux
Opened by Ray (ataraxia) - Wednesday, 17 March 2010, 01:41 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 18 August 2010, 18:47 GMT
Opened by Ray (ataraxia) - Wednesday, 17 March 2010, 01:41 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 18 August 2010, 18:47 GMT
|
DetailsUnlike the rest of the members of group base-devel, which are commonly used, ed and bin86 are much less often needed as makedeps, and would be better off just being listed in whichever PKGBUILDs actually need them. I'd like to be able to provide a list of such packages, but I can't think of how I'd do so.
Forum thread for this: http://bbs.archlinux.org/viewtopic.php?id=93283 |
This task depends upon
...
Optional Deps : ed: Interpret the patch as an ed script; for patch -e
functionality(deprecated)
So ed is not a real dep. I agree with remove these.
I routinely use ed to tweak configuration files, especially on systems like Arch that use the BSD vi.
Although it doesn't mention bin86 afaict so we could just remove bin86.
[posix link] http://www.opengroup.org/onlinepubs/9699919799/
Right, and lilo is in core. For some reason I thought lilo was in community.
Then bin86 should stay in core, but be removed from base-devel.