sborovic
/
dmzOS
1
2
Fork 1
Code Issues 8 Pull Requests Packages Projects 4 Releases Wiki Activity

WIP: Add the base containerized c toolchain environment #11

Closed
texhno wants to merge 0 commits from 10_env_image into main
pull from: 10_env_image
merge into: sborovic:main
Conversation 4 Commits - Files Changed -
texhno commented 2024-02-14 02:12:55 +00:00
Collaborator
Copy Link
No description provided.
texhno added 1 commit 2024-02-14 02:12:57 +00:00
texhno requested review from sborovic 2024-02-14 02:13:04 +00:00
texhno commented 2024-02-14 02:14:49 +00:00
Author
Collaborator
Copy Link

I opened this more as a chance to discuss about the process, than with the idea to have it merged.

I haven't got too much of an idea how this image should look like, or how it will interact with the project, where it should be placed in the codebase, and such. Would like to take this opportunity to discuss.

I opened this more as a chance to discuss about the process, than with the idea to have it merged. I haven't got too much of an idea how this image should look like, or how it will interact with the project, where it should be placed in the codebase, and such. Would like to take this opportunity to discuss.
texhno added 1 commit 2024-02-14 02:42:05 +00:00
sborovic commented 2024-02-14 08:55:25 +00:00
Owner
Copy Link

Add:

  • nasm

  • hd xxd

Add: - [x] nasm - [x] ~~hd~~ xxd
sborovic commented 2024-02-14 09:11:25 +00:00
Owner
Copy Link

This is essentially it.

docker-compose.yml needs to be placed in project root. I personally place all Dockerfile files in /Dockerfiles/.

Regarding vim, I think the best way to enforce project-level configuration is to use something like this. This means using local vim binary, but loading additional configuration (on top of an existing .vimrc) based on a project-level configuration file placed inside project root. I haven't actually used this before, just thinking out loud...

This is essentially it. docker-compose.yml needs to be placed in project root. I personally place all Dockerfile files in `/Dockerfiles/`. Regarding vim, I think the best way to enforce project-level configuration is to use something [like this](https://akrabat.com/using-vimrc-for-project-specific-settings/). This means using *local* vim binary, but loading additional configuration (on top of an existing `.vimrc`) based on a project-level configuration file placed inside project root. I haven't actually used this before, just thinking out loud...
sborovic changed title from Add the base containerized c toolchain environment to WIP: Add the base containerized c toolchain environment 2024-02-14 09:11:53 +00:00
texhno added 1 commit 2024-02-14 10:32:16 +00:00
sborovic commented 2024-02-15 17:21:39 +00:00
Owner
Copy Link

I have merged existing Wiki explanations with your proposed README changes into https://gitea.dmz.rs/sborovic/dmzOS/src/branch/main/README.md#development-environment. Does it look okay?

I'd review if all the software from the list above is actually available inside the image. After that, I think that pull request if ready to be closed.

EDIT: Also, as proposed README changes are conflicting maybe they can be removed from the pull request.

I have merged existing Wiki explanations with your proposed README changes into https://gitea.dmz.rs/sborovic/dmzOS/src/branch/main/README.md#development-environment. Does it look okay? I'd review if all the software from the list above is actually available inside the image. After that, I think that pull request if ready to be closed. EDIT: Also, as proposed README changes are conflicting maybe they can be removed from the pull request.
texhno added 1 commit 2024-02-16 18:49:33 +00:00
sborovic closed this pull request 2024-02-17 12:32:29 +00:00
sborovic deleted branch 10_env_image 2024-02-17 12:35:04 +00:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
sborovic
Labels
Clear labels   
bug

Something is not working

No Label
bug
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 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: sborovic/dmzOS#11
No description provided.
Delete Branch "10_env_image"

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?