Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
developer:nethserver_7_kickstart [2016/05/20 02:35]
Giacomo Sanchietti [Forked packages]
developer:nethserver_7_kickstart [2017/02/07 04:13] (current)
Davide Principi
Line 3: Line 3:
 ## Prerequisites ## Prerequisites
  
-Install ​CentOS ​on a development ​(virtual) machine. +Install ​NethServer ​7. Refer to [Administrator manual](http://docs.nethserver.org).
- +
-Latest CentOS version is 7.2.1511. +
- +
-Some related links: +
-  * https://​www.howtoforge.com/​centos-7-server +
-  * https://​www.youtube.com/​watch?​v=HQHPSq8RkiU +
- +
-Install YUM configuration for NethServer 7:  +
- +
-``` +
- # yum localinstall -y \ +
-    ​http://mirror.nethserver.org/​nethserver/​nethserver-release-7.rpm +
-``` +
- +
-Run the installation on CentOS command: +
- +
-``` +
- # nethserver-install +
-```+
  
 ## Developer environment ## Developer environment
Line 39: Line 20:
 passwd filippo passwd filippo
 </​file>​ </​file>​
- 
-Log-in on your development machine as created user, then add the following environment settings to ``~/​.bashrc``:​ 
- 
-```bash 
-export dist=ns7 ​ 
-export mockcfg=nethserver-7-x86_64 
-``` 
- 
-Then logout and login again, to have the environment updated or execute: 
- 
-``` 
- $ . ~/.bashrc 
-``` 
  
  
 ## GitHub-based workflow ## GitHub-based workflow
- 
-The initial work on NethServer 7 is an opportunity to test a GitHub-based workflow. This initiative has been decided on this [thread con community.nethserver.org](http://​community.nethserver.org/​t/​moving-from-redmine-to-github/​1530?​u=davidep). ​ 
  
 [Fork a repository](https://​help.github.com/​articles/​fork-a-repo/​) from [NethServer on GitHub](https://​github.com/​NethServer?​utf8=%E2%9C%93&​query=nethserver-). For instance, ``nethserver-directory``. [Fork a repository](https://​help.github.com/​articles/​fork-a-repo/​) from [NethServer on GitHub](https://​github.com/​NethServer?​utf8=%E2%9C%93&​query=nethserver-). For instance, ``nethserver-directory``.
- 
- 
  
 After a logout and login as a normal user,  clone locally your freshly forked repository: After a logout and login as a normal user,  clone locally your freshly forked repository:
Line 95: Line 59:
 As usual, if an error occurs during the RPM build or installation,​ check if the problem has been reported: As usual, if an error occurs during the RPM build or installation,​ check if the problem has been reported:
  
-* See if a similar problem is listed on [v7-alpha2 ​milestone](https://​github.com/​NethServer/​dev/​milestones/​v7-alpha2) or a [Pull Request](https://​github.com/​pulls?​user=NethServer) has been opened+* See if a similar problem is listed on [v7 milestone](https://​github.com/​NethServer/​dev/​milestones/​v7) or a [Pull Request](https://​github.com/​pulls?​user=NethServer) has been opened
  
-* Search ​on [development ​category in community.nethserver.org](http://​community.nethserver.org). We'​ll ​use the tag ``v7-alpha2``.+* Search ​the [development](http://community.nethserver.org/​c/​development) and [bug](http://​community.nethserver.org/c/bugcategories. We use the tag ``v7``.
  
-* Ask for help on community, opening a new topic [on development category](http://​community.nethserver.org/​c/​development) and adding the tag ``v7-alpha2``+* Ask for help on community, opening a new topic [on development category](http://​community.nethserver.org/​c/​development) and adding the tag ``v7``
  
-If you'​re ​sure the problem has never been found, file a new issue on \\ https://​github.com/​NethServer/​dev/​issues/​new+If you are sure the problem has never been found, file a new issue on \\ https://​github.com/​NethServer/​dev/​issues/​new
  
 * Build errors are usually written to ``build.log`` file, in your current working directory. ​ Search for relevant error messages inside ``build.log``. * Build errors are usually written to ``build.log`` file, in your current working directory. ​ Search for relevant error messages inside ``build.log``.