Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Download page is missing openSUSE rpms #20

Open
tigerfoot opened this issue Oct 23, 2016 · 7 comments
Open

Download page is missing openSUSE rpms #20

tigerfoot opened this issue Oct 23, 2016 · 7 comments

Comments

@tigerfoot
Copy link

in http://pgrouting.org/download.html
the location for openSUSE rpms could be added with this uri

http://download.opensuse.org/repositories/Application:/Geo/

People then choose to add their matching openSUSE (or SLE) version.

Also we offer another way to find the package by searching on http://software.opensuse.org

If you agree, I could certainly manage to create a patch for the page.

@dkastl
Copy link
Member

dkastl commented Oct 24, 2016

Thank you for the notice!
Of course you are welcome to change the website and send a pull request.
I think we should also add it to the pgRouting documentation.

This is the download.html source file for the website:
https://github.com/pgRouting/website/blob/master/download.rst
After modification I need to build the HTML files and update the gh-pages branch.

The pgRouting documentation covers installation topics with the following pages:
https://github.com/pgRouting/pgrouting/tree/develop/doc/src/installation
@cvvergara in this case, is it better to make pull requests for documentation changes to develop or masterbranch`?

@tigerfoot If you want me to add the links, let me know. But you're also free to describe more in details, how to install on SUSE.

@cvvergara
Copy link
Member

Personally, I would like to:

  • Get rid of the installation page in the documentation (except for some basic compilation)
  • Have a better wiki about installation because its easier for packaging people to update the information & then there is no need to rebuild/copy to gh-pages, publish and eventually make a release because of documentation changes.

@dkastl
Copy link
Member

dkastl commented Oct 24, 2016

The advantage of having the installation instructions together with the source code is, that it can change from one version to the next. Wiki pages tend to become outdated.

I'm not sure, we want to keep the page on the website though.

@cvvergara
Copy link
Member

For people that downloads the source there can be an INSTALLATION.txt

The README.txt can have a link to the wiki for downloads/installation guides
also the website can have the same link mentioned above

@cvvergara
Copy link
Member

@tigerfoot
What is what you usually do on other projects?

@tigerfoot
Copy link
Author

There's no absolute rules when I look at others upstream projects.
As I'm now packaging and maintaining the pgRouting module for openSUSE, I just like to have it published so people that are looking at pgRouting website see that they can use it with natives rpms.
For some projects, when there's a lot of after installation step we tend to have a readme.SUSE in the usr/share/doc/[package] where we instruct people how it work for SUSE.
So really feel free to reorganize the way you want to have thoses information published. I can adapt.
From my packager point of view, installation with source code should point to instruction directly in the pgRouting git repository, where (if not forgotten) important informations (changes, flags, deps etc) for builds are explicitely explained. But that's because I'm Lazy :-))

@cvvergara
Copy link
Member

Can be placed in the wiki, things are being moved there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants