Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 458750 - dev-libs/UTF8Strings : add USE=static-libs support
Summary: dev-libs/UTF8Strings : add USE=static-libs support
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: Normal enhancement (vote)
Assignee: Grigory
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-22 14:23 UTC by Agostino Sarubbo
Modified: 2013-02-22 17:15 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Solved issues (UTF8Strings-1.12.1.ebuild,505 bytes, text/plain)
2013-02-22 16:44 UTC, Grigory
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Agostino Sarubbo gentoo-dev 2013-02-22 14:23:02 UTC
We need to have USE=static-libs because this package install '.a' files:

usr/lib/libUTF8Strings-1.so
usr/lib/libUTF8Strings-1.a
Comment 1 Grigory 2013-02-22 16:44:01 UTC
Created attachment 339722 [details]
Solved issues

About .a files. I've inspected /usr/lib* directories and found that .a is very rare also I found that static linking is not popular and many users cancels .a files installing. So I have removed .a files building.

Also new package installs with FEATURES="multilib-strict" correctly.

Also I have a question. If source is changed and the last version is 0.12.0 how can it be 0.9 now? Can I just produce 0.12.1 with fixed bugs and stabilize it? Or I need to stabilize 0.1 too?
Comment 2 Agostino Sarubbo gentoo-dev 2013-02-22 16:48:37 UTC
Please push the 0.12.1 and we will stabilize that version
Comment 3 Tom Wijsman (TomWij) (RETIRED) gentoo-dev 2013-02-22 17:15:34 UTC
+  22 Feb 2013; Tom Wijsman <TomWij@gentoo.org> +UTF8Strings-1.12.1.ebuild,
+  UTF8Strings-1.12.0.ebuild, UTF8Strings-1.9.ebuild:
+  Version bump to 1.12.1 by Gorelov Grigory which supports multilib-strict,
+  removes .a files and is now EAPI=5. Fixes bug #458748 and #458750.

We can proceed stabilization now, I'll adjust the bug to stabilize 0.12.1 instead.

> If source is changed and the last version is 0.12.0 how can it be 0.9 now?

I'm not completely sure what you mean by that, but usually we try to keep multiple versions around so people can choose between them. For stabilization, versions which are longer in Portage and known to not have problems are considered first instead of newer and possibly more buggy versions.

Because we prefer to keep a buffer between stable and testing I've suggested to do 0.9 before; but since you had to fix some things we can move on to stabilizing 0.12.1 such that you don't have to port the fixes back, as 0.12.0 has been in Portage for long enough and this only introduces some minor fixes this should be possible to do. The arch teams agreed with that.