Remove vestigial SVN files #75

Open
opened 2024-06-05 12:27:18 +02:00 by ace-dent · 4 comments
Member

When we are 100% happy with the SVN --> git migration...

SVN relies on many duplicate copies of files, that are not needed under git. This bloats the repository size.

  • Remove all files under tag subdirectories (tags have already been setup on Git).
  • Carefully create branches under git, and copy files out of subdirectories into their own branch.
  • Move all files out of trunk subdirectories. This may require fixing relative and absolute file path references.
  • Cleanup hardcoded SVN references and comments: SVN, //svn., etc.
When we are 100% happy with the SVN --> git migration... SVN relies on many duplicate copies of files, that are not needed under git. This bloats the repository size. - [x] Remove all files under `tag` subdirectories (tags have already been setup on Git). - [ ] Carefully create `branches` under git, and copy files out of subdirectories into their own branch. - [ ] Move all files out of `trunk` subdirectories. This may require fixing relative and absolute file path references. - [ ] Cleanup hardcoded SVN references and comments: `SVN`, `//svn.`, etc.
ace-dent added the
Priority
Low
label 2025-04-05 20:33:33 +02:00
ace-dent added the
Category/General
Kind
Build
labels 2025-05-20 11:02:20 +02:00
Sweetbread referenced this issue from a commit 2025-05-20 17:36:16 +02:00
Author
Member

Question for the Dev community:

  • Do we want to keep tagged versions of FASM in KolibriOS source code?

We have 1.73, and also SVN tagged versions for 1.68 and 1.71. I propose removing the latter two.

Question for the Dev community: - Do we want to keep tagged versions of FASM in KolibriOS source code? We have [1.73](https://git.kolibrios.org/KolibriOS/kolibrios/src/branch/main/programs/develop/fasm), and also SVN tagged versions for [1.68 and 1.71](https://git.kolibrios.org/KolibriOS/kolibrios/src/branch/main/programs/develop/fasm/tags). I propose removing the latter two.
Owner

Do we want to keep tagged versions of FASM in KolibriOS source code?

Maybe it is kept for some compatibility, like old FASM in autobuild toolchain, or something like that.
Otherwise - I don't see practical reason in keeping it. But I may be wrong.

> Do we want to keep tagged versions of FASM in KolibriOS source code? Maybe it is kept for some compatibility, like old FASM in autobuild toolchain, or something like that. Otherwise - I don't see practical reason in keeping it. But I may be wrong.
Owner

Question for the Dev community:

  • Do we want to keep tagged versions of FASM in KolibriOS source code?

I believe they can be safely removed

> Question for the Dev community: > - Do we want to keep tagged versions of FASM in KolibriOS source code? I believe they can be safely removed
Author
Member

Thanks @Burer and @dunkaist for feedback. PR raised #268

Thanks @Burer and @dunkaist for feedback. PR raised #268
Sign in to join this conversation.
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KolibriOS/kolibrios#75
No description provided.