Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
abuild
abuild
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 25
    • Issues 25
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 16
    • Merge Requests 16
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • alpine
  • abuildabuild
  • Issues
  • #9986

Closed
Open
Opened Jan 06, 2020 by Drew DeVault@ddevaultContributor
  • Report abuse
  • New issue
Report abuse New issue

APKBUILD.5: propose rewriting in scdoc

I am the maintainer of scdoc: https://git.sr.ht/~sircmpwn/scdoc

Maintaining a man page by simply editing the roff macros by hand isn't a very sustainable approach. Additionally, the man pages are currently rendered with a fixed width, which makes them inconvenient to read down the road. I would like the ABUILD.5 man page to become the authoritative definition of APKBUILD syntax (obsoleting the corresponding wiki page), and I would like to expand the abuild docs with additional man pages. It would be easier to achieve these goals moving forward with a more comfortable syntax for writing the man pages in.

scdoc turned two a month ago and has experienced very little churn during its lifetime. It has been in community since Alpine 3.9. It requires only a C99 compiler and a conservative subset of POSIX to build, making it a trivial port to include while bootstrapping an Alpine system. The change would be very conservative when compared to other solutions like asciidoc.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: alpine/abuild#9986