Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
D dirsig-file-maker
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • dirsig_public
  • dirsig-file-maker
  • Issues
  • #5

Closed
Open
Created Jun 17, 2026 by Michael Blazej@michaelblazejMaintainer

Absolute Paths

Currently, the default functionality of dirfm is to write full absolute paths. It would be ideal, when building assets that get moved around, if paths were relative. When writing paths, check whether they are within the dirsig-input directory. If they are, a relative path is acceptable; if the path is outside the dirsig-input directory, I think it is still safe to use the absolute path.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking