Adding in opensuse, since this thread drifted on-topic! On Wed, Jul 6, 2016 at 1:21 PM, Carlos E. R. wrote:

On 2016-07-06 15:52, Greg Freemyer wrote:

...

On Wed, Jul 6, 2016 at 8:15 AM, Carlos E. R.

...

=== Getting dangerously close to on-topic, but take a look at this simple SR I did last night:

https://build.opensuse.org/request/show/406894

I suspect everyone active on this mailinglist has the technical skills to create SRs of that type.

Well, you have to know spec files :-) When I notice those mistakes, I write a bugzilla instead.

5 years ago the openSUSE devs would ask for bugzilla entries. Now they strongly prefer SRs. And they aren't that hard to do for simple issues. On the -factory mailinglist, the devs often ask for SRs, not bugzilla's.

...

fyi: The %doc directive in a tarball is special and a knowlegable user can do a package install and leave the docs uninstalled, so as far as I'm concerned there really isn't any good reason not to add the docs to the rpms.

rpm --excludedocs

Interesting. Was not aware of it. But disks are large, no problem for most people installing all docs, just in case.

Perhaps a switch in YaST or zypper config file to disable docs.

I didn't look. As you say, not something I worry about. RE: large disks - SSDs are becoming the norm and even 125 GB is over $50, so for me space is becoming important again on some of my machines. Also in VMs space can be important.

...

For some of the packages I care about, I've written and/or updated README.suse files and added them a package via SR.

Here's an example: https://build.opensuse.org/request/show/304713

Well, thanks.

I might modify or add to a readme, but a SR is still beyond my abilities.

SR => Submit Request To modify a readme you have to do a SR: ===== One time setup === - via web browser login into build.opensuse.org (with your normal bugzilla creds) When you do that that first time your home project is setup. You only have to do that once, but you MUST do it before you can do anything from the command line, etc. - from your openSUSE CLI sudo zypper in osc quilt mkdir ~/obs (Or whatever top level dir you want to use. I like obs for this) osc ls Archiving (answer questions about creds) Archiving is just a relatively small project that is easy to list out, but it won't work until you have your home project and credentials setup. ==== End of one time setup ==== - from your openSUSE CLI cd ~/obs (or whatever you named your top level working dir) osc bco <package> # by default the above: # - determines the devel project for the package # - creates a new sub-project in your home project to hold the branch # - branches a copy of the package from the devel project to the new sub-project # note the name of the sub-project that this command created ls # verify the new directory was created cd ls # verify a directory exists for the package you want to work on cd <package> # to edit an existing README.suse (etc.) vi README.suse osc vc (to create a changelog describing your edit) osc diff (to confirm you've made the changes you want) osc commit (commits the changes back to YOUR sub-project on the server) osc sr (send the change to devel project maintainer) Once your SR is accepted, you can delete the sub-project. (I do it via the webui, or you can use osc.)

-- Cheers / Saludos,

Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

Pat yourself on the back for having made a semi-permanent change to a openSUSE package. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org