synit
/
synit
1
0
Fork 1
Code Issues 2 Pull Requests 1 Projects Releases Wiki Activity

Figure out how to label some kind of reproducible release #5

New Issue
Open
opened 2023-10-18 23:46:27 +00:00 by tonyg · 0 comments
tonyg commented 2023-10-18 23:46:27 +00:00
Owner
Copy Link

At present, the code just takes whichever PostmarketOS/Alpine package contents happen to be around. It'd be nice if we could refer to something stable and build atop that. Then we could name a synit "distro" release that had some chance of being able to be built and run months after its release. At present, PostmarketOS and Alpine drift away from us, making bitrot a problem.

At present, the code just takes whichever PostmarketOS/Alpine package contents happen to be around. It'd be nice if we could refer to something stable and build atop that. Then we could name a synit "distro" release that had some chance of being able to be built and run months after its release. At present, PostmarketOS and Alpine drift away from us, making bitrot a problem.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: synit/synit#5
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?