version-release for different branches
by "Germán A. Racca"
Hi list,
I have the following situation. I have a package whose version-release
in f17/16 is 0.1.14-2, but in f18/master branches it is 0.1.14-3
(because of a f18 mass rebuild). Suppose I'm going to update the spec
file, so in f18/master branches the new version-release will be
0.1.14-4, and for f17/16 branches if I "git merge master", then the
release will jump from 2 to 4. Is this ok? Or should I keep working with
different releases for different branches and forget about "git merge
master" in lower branches?
All the best,
Germán.
--
Germán A. Racca
Fedora Package Maintainer
https://fedoraproject.org/wiki/User:Skytux
11 years, 7 months
Should {NEWS, CHANGELOG, README, etc} go into main package or -doc subpackage?
by Vít Ondruch
Hi,
Can somebody clarify where should go the files mentioned in $SUBJECT if
the package provides a -doc subpackage? It is obvious that the LICENSE
file must go into the main package, but what about the others? There are
packages, which has the $SUBJECT files in main package, but I think they
should go into -doc subpackage. What else wold be the -doc subpackage
purpose then?
BTW it would be nice if the guidelines could be clarified regarding this
issue.
Thank you
Vit
11 years, 7 months
php/php53 application packaging
by indent man
Hello,
I'm packaging a PHP application under CentOS 5.
It depends on some other php libraries, but should work with both php (5.1)
and php53.
But when I try to install the application RPM, yum mixes both php and php53
libraries.
What is the best way to prevent this ?
Cheers,
11 years, 7 months
When to use a leading underscore?
by Björn Persson
As maintainer of fedora-gnat-project-common I sometimes work on RPM macros for
use in Ada packages. Every time I define a new macro I have trouble deciding
whether its name should begin with an underscore or not. I know that there is
some technical difference but I've never quite understood what practical
difference it makes.
I've been trying to imitate macros with a similar function, so I defined
_GNAT_project_dir with a leading underscore in analogy with _libdir and
others. Macros containing command line flags for build tools I've defined
without a leading underscore in analogy with optflags, but then there are
_smp_mflags and the hardening macros which have the underscore, and
__global_cflags and __global_ldflags even have two leading underscores.
Could someone explain what difference a leading underscore makes and give some
guidance on when I should use it?
Is a double leading underscore functionally different from a single one, or is
that just some kind of naming convention?
Björn Persson
11 years, 7 months
