January 2015 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Opera package with Presto and Blink
by Christoph Grüninger 15 Jan '15

15 Jan '15

Hi openSuse! Currently we are stuck with an outdated version of Opera 12, the last release of Opera with its own engine Presto and their included email client M2. This package is called "opera". Opera decided to drop Presto and use WebKit and now Blink, beginning with Opera 15. The browser was re-written from scratch and misses features many users don't want to miss. Long time there was no Linux version. With Opera 25 there is an official Linux version available, it is released as a x64 binary Debian package. In OBS is a package for Opera 26, cf. home:XRevan86:non-free/opera. XRevan86 requested several merges to the upstream Opera package, but was declined, I don't now why. I propose to keep the old Opera 12 package as "opera12" or "opera-presto" and include XRevan86's package as a new "opera" package. What do you think? Is there a reason not to do so? Bye Christoph -- Wir haben eine Generation, die Autofahren als Ablenkung vom SMS-Schreiben empfindet. -- Daimler-Manager Ralf Herrtwich -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 4

[opensuse-packaging] patch names: maybe include patch numbers?
by Bernhard Voelker 13 Jan '15

13 Jan '15

Wouldn't it be good to have the number of the patch (as specified in the .spec file) in the names of the patches? Something like e.g.: Patch201: p201-fix-foo.patch Patch202: p202-avoid-crash-in-bar.patch Patch203: p203-improve-donald.patch Patch204: p204-add-cool-xyz-feature.patch I guess moving the patches around in the sequence is not that common, so this might help clarifying the order at the first glance. WDYT? The wiki [0] and alike are not that specific about this. [0] https://en.opensuse.org/openSUSE:Packaging_Patches_guidelines#Patch_naming Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

8 14

[opensuse-packaging] Using autogen.sh in a spec file?
by Johannes Kastl 12 Jan '15

12 Jan '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, sorry if this is an old hat, but I just stumbled upon it. lxc changed the sources layout between 1.0.x and 1.1, and no longer directly includes a configure file. So it has to be generated via ./autogen.sh. What's the right way to do this in a spec file? Just call the autogen.sh script? Or is there a macro for it? I found an older mail from Ludwig (and others), where %_configure is being redefined to run autogen.sh http://lists.opensuse.org/opensuse-packaging/2011-02/msg00032.html Regards, Johannes - -- Having a 'non-smoking' section in a restaurant is like having a 'non-peeing' section in a pool. (Robin Cowdrey) -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlSGCLsACgkQzi3gQ/xETbIwhgCdG6lr0laxVh9Nx6S5PrY5T3kv T70AoIaU6xzPExgSlKd7mteIPRMsyi2b =iO+j -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 9

[opensuse-packaging] About patching .po and .gmo files
by jcsl 10 Jan '15

10 Jan '15

Hi. I've updated the Spanish translation for Obconf. I've submitted the file upstream but in the meantime I want to add it to the package in the repos. If I only include the es.po patch (because es.gmo is a binary file) the updated translation isn't applied. I think that OBS copies the .gmo files directly. How do I manage this? Do I have to upload the .gmo file and copy it in the install phase of the spec file? Greetings. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 4

[opensuse-packaging] Go library packaging guidelines
by Thomas Boerger 09 Jan '15

09 Jan '15

Hi, i would like to discuss the current go library packaging guidelines. In my opinion we have to add the user or organization part of libraries hosted on github or bitbucket. As I’m currently working on some Go packages i realized that there are so many different „cli“ libraries or simply named „go“ or „core“. Following the naming scheme we have to name them „go-cli“, „go-go“ and „go-core“. Everybody knows how much different libraries we can cover that way. While i tried to package another library i ran into another issue. There are go libraries that depend on each other. Like https://github.com/shurcooL/go/blob/master/github_flavored_markdown/main.go <https://github.com/shurcooL/go/blob/master/github_flavored_markdown/main.go> and https://github.com/russross/blackfriday/blob/master/block.go <https://github.com/russross/blackfriday/blob/master/block.go>, which will be named „go-go“ and „go-blackfriday“. They are imported each other which won’t work with seperate packages. How should we solve something like that? Regards, Thomas Boerger

1 0

[opensuse-packaging] update and new package
by Eric Schirra 05 Jan '15

05 Jan '15

Hello, i have made updates for wammu and gammu in my home repo (home:ecsos). Building gammu needs a new package python-sphinxcontrib-breathe. This package i have build in my home repo too. So i want to make an request for wammu and gammu, but first i want to move the new package python-sphinxcontrib-breathe to repo hardware, so gammu can build. Who can create this new package so i can move it? Or what must i do to generate the new package in repo hardware? best regards Eric -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 5