On 4 April 2013 at 13:33, m.eik michalke wrote:
| hi,
|
| Am Mittwoch, 3. April 2013, 14:11:40 schrieb Dirk Eddelbuettel:
| > [ We could "one day" rename all non-standard source package names.
| > Apparently some people on the kernel team are not too happy with source
| > package "boot" -- should really be r-cran-boot ]
|
| shall i open a new bug? with the current solution, r-cran.mk is now ignoring
| the "Debain R Policy" in certain cases, again.
|
| i'm a little worried this might be forgotten otherwise, since the bug is now
| marked "solved", although the solution re-introduced an erroneous
| implementation and thereby simply makes buggy package names invisible again.
| it should rather be marked "postponed", if there was such a status.
We cannot break exiting r-cran-* packages. We have 150+ of them.
Try to accomodate your needs within roxyPackage.
| > Anyway, patch reversed, 3.0.0-2 is out. Old (working) behaviour and archive
| > buildability restored. That does come first.
|
| sure, i'm just confused how the actual policy can be fully implemented in
| another CRAN package, roxyPackage[1] (function debianize()), which has been
| the reason why i came up with the patch in the first place.
|
| there are a couple of R plugin packages for RKWard[2,3] which we would like
to
rwkward has been Debian package since 2005.
| debianize, and it seems we have two choices: violate the policy and create
| invalid package names which will build (but must all be renamed "one day"),
or
| adhere to the policy and be unable to build packages (i.e., have no debain
| packages at all).
|
| i see two possible *actual* solutions:
| - either change the policy to officially allow dots in package names,
| - or re-fix r-cran.mk and also fix all packages with invalid names.
The Debian R Policy does not matter. You are referring to a 10-year _draft_
document.
The corpus of 150+ r-cran-* and r-{other,bioc,...}-* packages matters.
Dirk
--
Dirk Eddelbuettel | [email protected] | http://dirk.eddelbuettel.com
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
