Skip to main content
Topic: Goodbye Github (Read 659 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Goodbye Github

Reply #1
How to register your account ?

Re: Goodbye Github

Reply #2
Before on GitHub if I wanted to download the pkgbuild and related files to build an Artix package I could use svn to get just those files and not the whole repo in a single command. Some packages have several files so it is time consuming to copy, paste, and name them manually. But now when I try this on the new repo it fails with an authentication error, and asks for a password.

Code: [Select]
svn export https://github.com/artix-linux/packages/trunk/openrc/repos/core-x86_64
svn export https://gitea.artixlinux.org/artix/packages/trunk/openrc/repos/core-x86_64

Perhaps there is a better way to do this, and it is not at all urgent or a big problem.  8)

Re: Goodbye Github

Reply #3
Before on GitHub if I wanted to download the pkgbuild and related files to build an Artix package I could use svn to get just those files and not the whole repo in a single command. Some packages have several files so it is time consuming to copy, paste, and name them manually. But now when I try this on the new repo it fails with an authentication error, and asks for a password.

Code: [Select]
svn export https://github.com/artix-linux/packages/trunk/openrc/repos/core-x86_64
svn export https://gitea.artixlinux.org/artix/packages/trunk/openrc/repos/core-x86_64

Perhaps there is a better way to do this, and it is not at all urgent or a big problem.  8)

You can clone per package with

Code: [Select]
git clone https://gitea.artixlinux.org/packages/<name-of-package>.git
the runit guy on artix

Re: Goodbye Github

Reply #4
Thank you for that, it works pretty well, but you get 2 copies, while with svn you only got 1:
Code: [Select]
$ ls -R
.:
openrc

./openrc:
repos  trunk

./openrc/repos:
core-x86_64

./openrc/repos/core-x86_64:
openrc-hook  openrc.install  openrc-install.hook  openrc.logrotate  openrc-remove.hook  PKGBUILD  sysctl.conf  sysctl.hook

./openrc/trunk:
openrc-hook  openrc.install  openrc-install.hook  openrc.logrotate  openrc-remove.hook  PKGBUILD  sysctl.conf  sysctl.hook

I think the trunk directory is probably intended for svn use, copied from the GitHub setup, so I suppose you could do away with it and make it git only which would work better with git. Or it looks like svn access could possibly be fixed by altering the server permissions to create a read only svn repo so it works like GitHub:
https://serverfault.com/questions/212097/svn-how-to-setup-a-read-only-branch-in-subversion

Re: Goodbye Github

Reply #5
Thank you for that, it works pretty well, but you get 2 copies, while with svn you only got 1:
Code: [Select]
$ ls -R
.:
openrc

./openrc:
repos  trunk

./openrc/repos:
core-x86_64

./openrc/repos/core-x86_64:
openrc-hook  openrc.install  openrc-install.hook  openrc.logrotate  openrc-remove.hook  PKGBUILD  sysctl.conf  sysctl.hook

./openrc/trunk:
openrc-hook  openrc.install  openrc-install.hook  openrc.logrotate  openrc-remove.hook  PKGBUILD  sysctl.conf  sysctl.hook

I think the trunk directory is probably intended for svn use, copied from the GitHub setup, so I suppose you could do away with it and make it git only which would work better with git. Or it looks like svn access could possibly be fixed by altering the server permissions to create a read only svn repo so it works like GitHub:
https://serverfault.com/questions/212097/svn-how-to-setup-a-read-only-branch-in-subversion


We do not use subversion.

The reason for the trunk, and yes its originating in arch's usage of svn, is to have a safe anchor for package removal from a repo.
Trunk is gonna remain, it serves a specific purpose.
As konimex pointed out, you can clone simply a package repo with git.

Re: Goodbye Github

Reply #6
Glad to hear the explanation - I only recently started using subversion as well as git because it was useful to download particular folders on GitHub, which for some reason was the easiest way to do that there.  :o

Re: Goodbye Github

Reply #7
OK, thanks for the work.

Will it stay consistent, that the subdirectories will be 'core-*', 'extra-*' and 'community-*' when the packages in Artix Linux will be from 'system', 'world' and 'galaxy', respectively?

I am working on some scripting to automatically find the right subdirectory depending on the repository, so I need some consistency and that information.

Re: Goodbye Github

Reply #8
Naming is the same.

Just look around.

You may also find this helpful.