Activate NethForge directly from the software center

alefattorini · February 2, 2016, 10:56pm

Continuing the discussion from Call for test Stephdl modules:

Jim · February 3, 2016, 1:15am

I see this Nethforge as the AUR repository in the Archlinux environment.

With all warning when clicking on the option… Why not?

giacomo · February 3, 2016, 7:53am

This is not simple at all.

The NethForge release RPM is not inside the default distribution
This can be simply addressed by installing the RPM with core modules, but would be the repository enabled by default?
Adding NethForge to left menu
What does exactly the purpose? You would like to replicate the “Software Center” target only for the forge?
Which repository from NethForge should be enabled by default?
Would like to see both stable and testing RPMs? If we want to enable only the stable repository, how would you enable the testing repository from the GUI (we totally miss, by purpose, this feature)?

Just to clarify a bit, I agree with this proposal but we need to get the right decisions since adding such a feature is not trivial

alefattorini · February 3, 2016, 8:46am

My purpose is giving to NethForge more visibility permitting the “config set repository” by webinterface. I would install the NethForge rpm repository into the core module and disabling it by default, giving the possibility to simply enable it by webui.
So that people can said "oh I see tons of interesting modules here … Cool!"
What do you think? Is it more clear now?

davidep · February 3, 2016, 8:57am

We’re not far from here. The nethserver-nethforge-release RPM is already in base repository:

http://mirror.nethserver.org/nethserver/6.7/base/x86_64/Packages/nethserver-nethforge-release-6.6-3.ns6.noarch.rpm

Nowadays a shell command is required to enable it, but we can easily add it to the Software Center by creating a YUM group here:

github.com

NethServer/comps/blob/master/nethserver-groups.xml.in

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE comps PUBLIC "-//Red Hat, Inc.//DTD Comps info//EN" "comps.dtd">
<!-- 
  Copyright (C) 2012 Nethesis S.r.l.
  @author Giacomo Sanchietti <giacomo.sanchietti@nethesis.it>
-->
<comps>

<!-- CENTOS GROUPS START -->

 <group>
    <id>buildsys-build</id>
    <_name>Build system</_name>
    <_description>Tools for building RPMs</_description>
    <default>false</default>
    <uservisible>false</uservisible>
    <packagelist>
      <packagereq type="default">bash</packagereq>
      <packagereq type="default">bzip2</packagereq>
      <packagereq type="default">coreutils</packagereq>

This file has been truncated. show original

Please, read the doc

http://docs.nethserver.org/projects/nethserver-devel/en/latest/package_groups.html

I’m waiting for your Pull Requests

giacomo · February 3, 2016, 1:51pm

So the proposal it’s something like this:

Add a NethForge groupo inside the base repository, then the user will be able to install the NethForge with a single click
The NethForge will enabled by default when installed, and a new “NethForge” category will be available inside the Software Center

Am I correct?
@dz00te what to you think?

davidep · February 3, 2016, 1:53pm

IIRC we already have this

github.com

NethServer/nethserver-nethforge-release/blob/master/NethForge.repo#L7


      
          [nethforge]
          name=NethForge $releasever
          mirrorlist=http://mirrorlist.nethserver.org/?release=$releasever&repo=nethforge&arch=$basearch&nsrelease=$nsrelease
          #baseurl=http://mirror.nethserver.org/nethserver/$releasever/nethforge/$basearch/
          gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-NethForge-7
          gpgcheck=1
          repo_gpgcheck=1
          enabled=1
          enablegroups=1
          
          [nethforge-testing]
          name=NethForge $releasever - Testing
          mirrorlist=http://mirrorlist.nethserver.org/?release=$releasever&repo=nethforge-testing&arch=$basearch&nsrelease=$nsrelease
          #baseurl=http://packages.nethserver.org/nethserver/$releasever/nethforge-testing/$basearch/
          gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-NethForge-7
          gpgcheck=1
          repo_gpgcheck=1

BTW baseurl was fixed for ns7

dz00te · February 3, 2016, 5:53pm

yes i think it’s ok, this will permit the installation of contribs in a easier way…

giacomo · February 4, 2016, 1:07pm

Ok, let’s go down this way!

giacomo · February 10, 2016, 2:39pm

Done on NS 7!

Of course, the phpMyAdmin is only an example!

Ctek · February 10, 2016, 7:09pm

That great @giacomo! You guys are giving us the cookies one after the other

mabeleira · February 17, 2016, 3:24pm

Love the idea.

Jim · March 10, 2016, 10:08pm

Reading the Owncloud 9 topic, I was thinking about the Nethforge repository.
I seem like the AUR Repository in Archlinux:

What about the stability?
What about the level of integration with the NethServer Core system? (Ie php version required)
What about the confidence about a package? ( stli maintened or not )

stephdl · March 10, 2016, 10:34pm

You have two repositories for nethforge…

Nethforge the stable repository
Nethforge-testing the staging repository for test purpose.

Normally when a rpm goes to nethforge you can be confident

Jim · March 10, 2016, 11:46pm

But the history, the actualization, security correction…it’s the Dev Team to care about or someone else ( the package creator, onother maintainer )?

stephdl · March 11, 2016, 6:20am

I suppose that the author is the best to follow security updates, but if he doesn’t follow them, others can do it.

I recall two rpm in nethforge, phpmyadmin and wordpress, concerning the security purpose the most of time it is to push new dependencies from epel to nethforge.

Jim · March 11, 2016, 9:58am

We have to find a way to control this.
Perhaps with a quality team, because there’s lot of things that can occur…
The author can die, can leave the project, can be too busy to continue to maintain.

stephdl · March 11, 2016, 12:37pm

Yeah…this is life

Jim · March 11, 2016, 1:07pm

For this reason we have to find something to prevent.
Societies, Enterprises, Associations, Projects have to prevent these inconvients…

giacomo · March 11, 2016, 2:26pm

This is the difference between packages inside the core and the forge.
Core packages are maintained and supported by the whole NethServer project, packages inside the forge are the effort of one or more developers who shared their work (often with time stolen to the family ).

Of course, core developers are always willing to help getting good packages inside the forge!