* [gentoo-dev] Package version in case of upstream patches from stable branch of development
@ 2010-08-03 12:03 99% Peter Volkov
0 siblings, 0 replies; 1+ results
From: Peter Volkov @ 2010-08-03 12:03 UTC (permalink / raw
To: gentoo-dev; +Cc: qa
Hi.
How should we version our packages in case we've backported upstream
patches from stable branch of development? Bug 330667 requests _p or
_pre. I feel that _p|_pre versions should be left for VCS (read
development) versions of the package, while during backports we have the
best version with all important upstream+gentoo fixes available to the
moment and I'd better avoid to call it development.
If we decide to go with _p or _pre could we agree on answers for the
following questions:
- Does single patch from upstream's VCS justify _p$(date|rev) version?
What if this is _the only_ patch in the upstream's VCS?
- Now what about two patches? Three? N? When does few patches became
pile?
- What if I drop single patch from the upstream's patchset for stable
branch, should we drop _pre _p version and add -rN?
- What if there are two dependent patches, and first one fixes
indentation? Should we spend time on backporting second patch (time
consuming and error prone process) or use both and live closer to
upstream?
I think without exact answers on this questions I don't think this bug
330667 may request anything, only suggest... But what do you think?
--
Peter.
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2010-08-03 12:03 99% [gentoo-dev] Package version in case of upstream patches from stable branch of development Peter Volkov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox