This patch allows short-circuiting of building binary packages. To
prevent accidental use of short-circuited rpms, they are marked with
an unsatisfiable dependency rpmlib(ShortCircuited). A developer using
this feature for local development and testing will use --nodeps.
Should such a rpm leak
A gentleman who wishes not to be named wrote:
You have no right to discuss the state of my mind.
I apologize for quoting a public message from you.
I apologize for infering anything about your opinion from the fact that
the software, of which you are the primary developer, has the feature.
Good
Deciding whether it is necessary to remove the SUID bit based on
the current link count creates an opportunity for a race condition.
A hardlink could be created just between lstat() and chmod().
This reverts commit 89be57ad9239c9ada0cba94a5003876b456d46bf.
---
lib/fsm.c |2 +-
1 files
On Mon, 21 Jun 2010 16:10:49 +0300 (EEST) Panu Matilainen wrote:
I would consider applying a -bb/-bs --short-circuit enabling patch if
the patch causes the resulting package to be poisoned, requiring
some extra switch to be installable. The developer in case 1) who
knows what [s]he's doing
This patch allows short-circuiting of building binary packages. To
prevent accidental use of short-circuited rpms, they are marked with
an unsatisfiable dependency rpmlib(ShortCircuited). A developer using
this feature for local development and testing will use --nodeps.
Should such a rpm leak