/g/ - Technology

install openbsd

[Make a Post]
[X]





Version Control System and Issue Tracking Nanonymous No.5609 [D][U][F][S][L][A][C] >>5610 >>5613 >>5791
File: 216db011adfae6a9a41b0049c938758488588547c26c2722ad3326e5aa5452e5.jpg (dl) (3.97 KiB)
What is the ultimate way for VCS and Issue Tracking?

Is Version Control System useful for personal projects developed by one person?
I tried some program but I did not like that it cloned my project files into another place. It also produced some folders. Which VCS is simplest in folder structure?
Also, what to do if I have project A, B, C. and those three project share some code between them? How to edit and commit that code? where should it belong? should the shared code be a separate project?

How about issue tracking? Is that needed in one man project? What software should I use for it?
How about using VCS for non-programming projects? What do you think?

Nanonymous No.5610 [D] >>5611
>>5609
>What is the ultimate way for VCS and Issue Tracking?
git is fine and has lot of literature about it
>Is Version Control System useful for personal projects developed by one person?
yes, very
>Which VCS is simplest in folder structure?
git keeps everything in one folder
>Also, what to do if I have project A, B, C. and those three project share some code between them?
put the shared code in a git submodule, then add the submodule to projects that needs it
>How about issue tracking? Is that needed in one man project?
do you mean you're the only developer or you're the only one that will use it?
if users needs a way to report bugs i guess you need it
>How about using VCS for non-programming projects?
for everything text-based that needs versioning it's prefect

Nanonymous No.5611 [D] >>5619 >>5791
>>5610
>git is fine and has lot of literature about it
I heard git is shit because it is hard to use and has some stupid commands as typical unix shit. I need something with GUI and big buttons so I click and it does everything for me

>Is Version Control System useful for personal projects developed by one person?
>yes, very
why? what advantages does it offer?

>git keeps everything in one folder
I assume it will still require two copies, one for working, editing files, and one where repository is stored?

>put the shared code in a git submodule, then add the submodule to projects that needs it
does other VCS offer submodule feature?

>do you mean you're the only developer or you're the only one that will use it?
the only one that will use it (at least for now)

>for everything text-based that needs versioning it's prefect
but what is "text-based" and what is not? is RTF (rich text format) still text-based? or if I have LibreOffice documents, spreadsheets, it won't work with VCS? or it will treat them as binary files

Nanonymous No.5612 [D]
https://pijul.org/
https://sourcehut.org/
http://git.2f30.org/stagit/

Nanonymous No.5613 [D] >>5619 >>5636
>>5609
>Which VCS is simplest in folder structure?
fossil has a single file containing your project, and a single dot-file indicating that you've opened the project
>what to do if I have project A, B, C. and those three project share some code
1. do not use git submodules
2. do not use git submodules
3. do not use git submodules
have your build system fetch the code as needed
>issue tracking
fossil provides this
>non-programming projects
I use fossil for tech writing as well as programming

Nanonymous No.5619 [D] >>5620 >>5636
>>5611
>I heard git is shit because it is hard to use
iIare learning it's good cause you are gonna find lot of resources written about it.
Being the industry standard you should be at least able to use it's basic functions or you are gonna be cut off of a lot of projects.
>Is Version Control System useful for personal projects developed by one person?
>yes, very
>why? what advantages does it offer?
It makes possible to track your progress with time and to organize your work better.
It allows you to go back to a previous version if you fuck up.
It allows you to work on experimental features in parallel branches.
>does other VCS offer submodule feature?
Sure.
>the only one that will use it (at least for now)
Then don't bother with issues tracking, keep it simple.
>but what is "text-based" and what is not?
There are two kind of files, binary like images,videos etc and plain-text like html files, json files, code in general.
RTF(if it contains formatting and images), spreadsheets etc are not plain-text.
>it won't work with VCS?
Even if it's a binary files it will still works with VCS, but it's not recommended cause it needs to copy the whole file at every commit instead of only the changes from last version. Methos like git LFS to make this more viable exist.

read https://git-scm.com/book/en/v2 they explain stuff better than me
>>5613
>do not use git submodules
For small project they are probably too much, but they have their use case.

Nanonymous No.5620 [D]
>>5619 (me)
First line got fucked up
>iIare learning it's good cause you are gonna find lot of resources written about it.
In my opinion it's not particularly hard to use, there are GUI implementations but you should really learn the commands and for learning it's good cause you are gonna find lot of resources written about it.

Nanonymous No.5621 [D] >>5636
If you are using git. I highly recommend using magit, an emacs package. It's such a good frontend, some people get emacs just to use it.

Nanonymous No.5636 [D] >>5640 >>5653
>>5613
>fossil has a single file containing your project
repository file?
>1. do not use git submodules
why?
>have your build system fetch the code as needed
what is build system? I just want to click on big buttons, what is the button to share code between projects?
also, not only I need to share code between project, the shared code will be edited while I edit the projects. So I need to commit the shared code too
>fossil provides this
but should I use issue tracking?
>I use fossil for tech writing as well as programming
isn't fossil without GUI? but only with shit web gui?

>>5619
>there are GUI implementations but you should really learn the commands
commands are for unix idiots, I am not wasting my time with commands and manuals
>Being the industry standard you should be at least able to use it's basic functions or you are gonna be cut off of a lot of projects.
that's correct. but I can use something better for my personal projects.
>It allows you to go back to a previous version if you fuck up. It allows you to work on experimental features in parallel branches.
if you need big change in code you can just copy or archive the files
>Even if it's a binary files it will still works with VCS, but it's not recommended cause it needs to copy the whole file at every commit instead of only the changes from last version.
why does it work that way? if only one byte of file changes it could just store that difference
>For small project they are probably too much, but they have their use case.
then how to share code between small projects?

>>5621
>If you are using git.
not decided yet. tell me what to use

>I highly recommend using magit, an emacs package. It's such a good frontend, some people get emacs just to use it.
so it's some kind of hack of another program that has nothing to do with VCS/git? sounds like typical unix brain damage, some shit glued with another shit to produce some primitive broken shit

Nanonymous No.5640 [D] >>5641 >>5683
>>5636
are you trolling?
but why

Nanonymous No.5641 [D] >>5643
>>5640
>are you trolling?
no. what makes you think so?
are you unix idiot living in unix bubble where everyone thinks unix is great?
go outside and compare unix shit with alternatives, open your eyes

Nanonymous No.5643 [D] >>5655
>>5641
idgaf what you think of unix and i won't take the bait
what bothers me is that you're not even willing to read the fucking gir book that i linked which is written for mentally damaged retards, i won't spoonfeed you any longer do your own research or don't bother with vcs, but since you're most probably trolling whatever, bye

Nanonymous No.5653 [D] >>5655
>>5636
>commands are for unix idiots, I am not wasting my time with commands and manuals
Then use magit.
>if you need big change in code you can just copy or archive the files
Git is a system which allows you to manage and store these copies.
>why does it work that way? if only one byte of file changes it could just store that difference
The problem is that you can't really merge binary diffs together. You might not even get a valid file after doing it. Also good luck trying to handle merge conflicts.
>tell me what to use
git
>so it's some kind of hack of another program that has nothing to do with VCS/git
GNU Emacs is a highly extensible text editor. Extensible enough that someone made a frontend for git with it.
>sounds like typical unix brain damage
Emacs does not originate from UNIX and has a very different approach.

Nanonymous No.5655 [D] >>5660
>>5643
>what bothers me is that you're not even willing to read the fucking gir book that i linked which is written for mentally damaged retards
I did not read git manual because I have not yet decided to use git
first I need to choose what VCS will I use, then I need to read manual about it

>>5653
>Git is a system which allows you to manage and store these copies.
yes, but I am pointing that for simple cases you don't need it, it's easier to just copy paste code
>The problem is that you can't really merge binary diffs together.
why not? just store where has it changed, on what bytes
>Also good luck trying to handle merge conflicts.
I don't see why not. and even if it's not possible, instead of merging it by VCS, user could open the file and merge them manually.
>git
why git
why not other systems
>GNU Emacs is a highly extensible text editor. Extensible enough that someone made a frontend for git with it.
why should I manage VCS in text editor instead of in VCS manager?

Nanonymous No.5660 [D]
>>5655
>why should I manage VCS in text editor instead of in VCS manager?
Because magit is the best version control interface that currently exists.

Nanonymous No.5683 [D] >>5688 >>5709
>>5640
Full on /tech/ invasion brought over the all the anti-unix disciples

Nanonymous No.5688 [D]
>>5683
That's obviously a windows luser, it's not the same.

Nanonymous No.5709 [D]
>>5683
>this is what Cniles really think

Nanonymous No.5778 [D]
what version system is best and why?

Nanonymous No.5779 [D] >>5780 >>5781
Got (Game of Trees) is being developed by phessler@ (OpenBSD developer):
https://twitter.com/phessler/status/1159817679785607168

Nanonymous No.5780 [D]
>>5779 (me)
http://gameoftrees.org/

Nanonymous No.5781 [D]
>>5779 (me)
Actually the main dev is stsp@ not phessler (but he is helping too, it seems).

Nanonymous No.5783 [D]
how to manage my projects in git or other vcs
should I have separate repository for each project? or group of projects?
what about shared code, libraries, modules?

Nanonymous No.5791 [D][U][F]
File: f4f8716236656f7e6796b2f44a91a924dc11f5003df4967565ae36805d4e83ef.jpg (dl) (185.99 KiB)
>>5609
>Also, what to do if I have project A, B, C. and those three project share some code between them? How to edit and commit that code? where should it belong?
https://en.wikipedia.org/wiki/Library_(computing)
>>5611
>I heard git is shit
I heard your mother's a whore. I guess we both "heard" stuff. Do you have data? Do you have an argument? Or do you just have
>I heard
?
That said, if you're planning on being a one-man shop, it doesn't really matter what you use, as long as it's a currently-supported VCS that's not subject to bitrot in the near term. Use svn. Use git. Use fossil. Use hg. Doesn't matter. For an individual user, even rcs would probably be fine. Pick one, learn to use it, and move the fuck on. Individuals doing useful programming don't need to masturbate endlessly about this topic.