[Pkg-bitcoin-devel] Packaging alternative to bitcoin core, the return

Amaury SECHET deadalnix at gmail.com
Thu Feb 2 16:30:49 UTC 2017


2017-02-01 18:22 GMT+01:00 Jonas Smedegaard <jonas at jones.dk>:

>
> Your picking this particular "low-hanging fruit" potentially does more
> harm than good.  I recommend that you don't - let an existing maintainer
> do that work (or explicitly acknowledge that you do it with them or
> instead of them - then taking over as new maintainer).
>
>
Alright, you are the boss. I'm available to help with packaging that thing,
but if you think that's a bad idea, then so be it.


> >> If you are talking about how to bootstrap a package _based_ on
> >> existing Bitcoin package, then please try rephrase your question - I
> >> don't quite follow what your plan is, and how you are lost in that
> >> plan of yours.
> >>
> > As I'm learning how all of this work, I'm figuring out how I can
> > provide value along the way. My first step was to get the current
> > package to build and all to get familiar with the tech. My second step
> > is to modify this to package an alternative.
>
> Sounds fine, described broadly as you do above.  My concern here is the
> risk of your screwing up causes _more_ work for me or others - work that
> we have shown to lack in recent time in this team.
>
> Therefore I strongly recommend that you explore options without risk of
> breaking existing packages.
>
>
Got you. I'll focus on getting the alternative packaged without touching
the original package.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/attachments/20170202/d2c0970b/attachment.html>


More information about the Pkg-bitcoin-devel mailing list