Re: package sponsorship request
I am also confused about the distinction you are trying to draw
between "sponsoring" and "adoption". I am not wanting to give up this
package forever yet. I am hoping to find another avenue to get it
into Debian. In the past certain DD's have uploaded it for me, and I
am due to become one soon. I am wanting to give up (for a time) on
trying to learn a lesson that is too hard for me to grasp while there
is another goal to get software out to those who want to use it, like
Michael Hanke. I do not think it is appropriate to keep making him
wait weeks (after he so nicely sent in a working patch) while we
disagree over location of credit-lines when all are reasonably
accurate. And I do not think it is appropriate to ignore the policy
decisions of maintainers who are trying to retain consistency across
all their packages over multiyear plans: e.g. all my packages are
tending (standardizing) towards autoconf, automake, cdbs, and
consistent THANKS + AUTHORS files. This is my policy decision, it
seems logical, and I don't understand how it can be counter Debian.
If it is please explain in other words so I can grasp the point.
Best regards,
Rudi
On 10/5/07, Rudi Cilibrasi <cilibrar@gmail.com> wrote:
> Hi everybody,
>
> Sorry to be so excited. Here is the now-public hg repository:
>
> hg clone http://hg.cilibrar.com/pkg-libsvm/
>
> I welcome all changes that are technically or informationally
> beneficial and are going to help this quickly get in Debian. I do not
> want to switch packaging systems at this time because it makes more
> sense to wait until the package switches completely with me as
> upstream (maybe with a different name) and I re-enable the
> autoconf/automake stuff that is currently not visible but on my
> computer somewhere for later. Cheers, -r.
>
> On 10/5/07, Rudi Cilibrasi <cilibrar@gmail.com> wrote:
> > Thanks for this awesome tip. It is actually a big winner and I will
> > be using it a lot in the future to avoid writing all the useless files
> > for every new project.
> >
> > > As far as this particular issue goes, have you considered simply
> > > running automake --foreign ?
> >
> > This, of course, is a game-changer on my packaging policy (looks like
> > a way to simplify) so I will be doing that in the future. However,
> > the AUTHORS and THANKS files serve another purpose in this case
> > besides letting (simply-invoked)
> > automake succeed. They also help explain that my friend Chih-Jen and
> > his friend Chih Chung wrote the core math code together, but I myself
> > wrote the manpages, packaging related files, and some new features
> > that Chih-Jen did not accept, like the quiet option. This is
> > essential to be in Debian but since Chih-Jen never agreed with the
> > feature enhancement I felt it important to distinguish who added it in
> > these new files. Because I don't want to add things under his name.
> > That is why I clarified who wrote what the way I did as I thought was
> > standard creditting policy.
> >
> > BTW the source is not on alioth yet it is downloadable as a tar (but
> > not automatically) from the web and I have a Mercurial repos here with
> > the packaging files. I can put it up on a public Mercurial URL
> > (http:) on my server but I am not sure if I have enough access to put
> > it up on alioth or not yet ; my Debian account is still waiting.
> > Cheers,
> > -r.
> > On 10/5/07, Aaron M. Ucko <ucko@debian.org> wrote:
> > > "Rudi Cilibrasi" <cilibrar@gmail.com> writes:
> > >
> > > > Michael Koch believes it is inappropriate for me to be changing
> > > > AUTHORS and THANKS. Actually, I made those up quite some time ago to
> > > > allow for automake to be used in packaging (optionally). But, he
> > >
> > >
> > > --
> > > Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
> > > http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?amu@monk.mit.edu
> > >
> >
> >
> > --
> > "We can try to do it by breaking free of the mental prison of
> > separation and exclusion and see the world in its interconnectedness
> > and non-separability, allowing new alternatives to emerge." -- after
> > Vandana Shiva
> >
>
>
> --
> "We can try to do it by breaking free of the mental prison of
> separation and exclusion and see the world in its interconnectedness
> and non-separability, allowing new alternatives to emerge." -- after
> Vandana Shiva
>
--
"We can try to do it by breaking free of the mental prison of
separation and exclusion and see the world in its interconnectedness
and non-separability, allowing new alternatives to emerge." -- after
Vandana Shiva
Reply to: