snailed
/
void-packages
2
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Activity

change URLs to new Github organization 

closes #140
This commit is contained in:
Daniel Lewan 2018-06-16 16:42:17 +02:00 committed by Enno Boland
parent ab0e56ef82
commit bbf6cad158
3 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
CONTRIBUTING.md
View File

@ -7,9 +7,9 @@ This document describes how you as a contributor can help adding packages, corre
## Getting your packages into Void by yourself
If you really want to get a package into Void Linux we recommend you to package it yourself.
We provide a [comprehensive Manual](https://github.com/voidlinux/void-packages/blob/master/Manual.md)
We provide a [comprehensive Manual](https://github.com/void-linux/void-packages/blob/master/Manual.md)
on how you can create new packages. Also there's a
[manual about xbps-src](https://github.com/voidlinux/void-packages/blob/master/README.md) which is used
[manual about xbps-src](https://github.com/void-linux/void-packages/blob/master/README.md) which is used
to build package files from templates.
For this guide, we assume you have basic knowledge about [git](http://git-scm.org) and a [GitHub Account](http://github.com)
@ -21,7 +21,7 @@ as specific git- or svn-revisions anymore.
templates must be placed in `void-packages/srcpkgs/<pkgname>/template` where `pkgname` is the same as the pkgname variable in the template.
For deeper insights on the contents of template files consider reading the [manual](https://github.com/voidlinux/void-packages/blob/master/Manual.md)
For deeper insights on the contents of template files consider reading the [manual](https://github.com/void-linux/void-packages/blob/master/Manual.md)
There's a helper tool for creating new packages in the [xtools](https://github.com/chneukirchen/xtools) package:
@ -33,18 +33,18 @@ There's a helper tool for creating new packages in the [xtools](https://github.c
Once you have built your template files there are certain rules on how the commit should be named.
* Use the following for newly added packages: ```New package: <pkgname>-<version>```
[Example](https://github.com/voidlinux/void-packages/commit/176d9655429188aac10cd229827f99b72982ab10)
[Example](https://github.com/void-linux/void-packages/commit/176d9655429188aac10cd229827f99b72982ab10)
* Use the following if you update a package: ```<pkgname>: update to <version>.```
[Example](https://github.com/voidlinux/void-packages/commit/b6b82dcbd4aeea5fc37a32e4b6a8dd8bd980d5a3)
[Example](https://github.com/void-linux/void-packages/commit/b6b82dcbd4aeea5fc37a32e4b6a8dd8bd980d5a3)
* If you changed something on the template without a version change use ```<pkgname>: <reason>```
[Example](https://github.com/voidlinux/void-packages/commit/8b68d6bf1eb997cd5e7c095acd040e2c5379c91d)
[Example](https://github.com/void-linux/void-packages/commit/8b68d6bf1eb997cd5e7c095acd040e2c5379c91d)
If you want to describe your changes in more detail, make an empty line and add the description afterwards.
[Example](https://github.com/voidlinux/void-packages/commit/f1c45a502086ba1952f23ace9084a870ce437bc6)
[Example](https://github.com/void-linux/void-packages/commit/f1c45a502086ba1952f23ace9084a870ce437bc6)
This is also described in the [manual](https://github.com/voidlinux/void-packages/blob/master/Manual.md) in deeper detail.
This is also described in the [manual](https://github.com/void-linux/void-packages/blob/master/Manual.md) in deeper detail.
There's a helper tool for committing packages in the [xtools](https://github.com/chneukirchen/xtools) package:

2
Manual.md
View File

@ -1275,7 +1275,7 @@ You can now make your own commits to the `forked` repository:
To keep your forked repository always up to date, setup the `upstream` remote
to pull in new changes:
$ git remote add upstream git://github.com/voidlinux/void-packages.git
$ git remote add upstream git://github.com/void-linux/void-packages.git
$ git pull upstream master
Once you've made changes to your `forked` repository you can submit

8
README.md
View File

@ -79,7 +79,7 @@ To enable it:
Clone the `void-packages` git repository, install the bootstrap packages:
```
$ git clone git://github.com/voidlinux/void-packages.git
$ git clone git://github.com/void-linux/void-packages.git
$ cd void-packages
$ ./xbps-src binary-bootstrap
```
@ -363,7 +363,7 @@ If your system does not support `user namespaces`, a privileged group is require
Clone the `void-packages` git repository:
$ git clone git://github.com/voidlinux/void-packages
$ git clone git://github.com/void-linux/void-packages
and `xbps-src` should be fully functional; just start the `bootstrap` process, i.e:
@ -440,7 +440,7 @@ Once the build has finished, you can specify the path to the local repository to
### Contributing
See [Contributing](https://github.com/voidlinux/xbps-packages/blob/master/CONTRIBUTING.md)
See [Contributing](https://github.com/void-linux/xbps-packages/blob/master/CONTRIBUTING.md)
for a general overview of how to contribute and the
[Manual](https://github.com/voidlinux/xbps-packages/blob/master/Manual.md)
[Manual](https://github.com/void-linux/xbps-packages/blob/master/Manual.md)
for details of how to create source packages.