Bug#602050: ITP: supercollider -- A real time audio synthesis programming language
- To: Felipe Sateler <fsateler@debian.org>
- Cc: 602050@bugs.debian.org, Debian Multimedia Packages Maintainers <pkg-multimedia-maintainers@lists.alioth.debian.org>
- Subject: Bug#602050: ITP: supercollider -- A real time audio synthesis programming language
- From: Dan S <danstowell+debmm@gmail.com>
- Date: Sat, 11 Jun 2011 15:07:01 +0100
- Message-id: <[🔎] BANLkTinVQ63Ca+6AnNBJSVJCoADOMjsWRQ@mail.gmail.com>
- Reply-to: Dan S <danstowell+debmm@gmail.com>, 602050@bugs.debian.org
- In-reply-to: <BANLkTi=LTfXF6xycQv4iYTm319Qbr8OwQQ@mail.gmail.com>
- References: <20101031232754.19021.43862.reportbug@pcfelipe.sateler> <AANLkTinB0TzagQpkeQD8dVr8T0RH=4jjLfSm2s=Rc0Ae@mail.gmail.com> <AANLkTik7YZ0WOCkDZ32Vp3J17FRzaD=504rtJGr2G2O9@mail.gmail.com> <AANLkTi=uziSawDVeUtgDH2jkqGpVWwvUS-kvdT8ZHGbA@mail.gmail.com> <AANLkTi=L-ETos83uv_--qPQdEQptduaTJvsgisurMUYR@mail.gmail.com> <AANLkTinbnQvdSp=vybxSO419MaktS8NQeT=h8JCxQ5jS@mail.gmail.com> <AANLkTikL9bbDnvrbfGg9+7jJg80nmaDj+Oj=ZUkT0wEO@mail.gmail.com> <AANLkTimwV=0yacGfKL5ANBg0qm19fj-5XkNg8QqW1kJL@mail.gmail.com> <AANLkTinzvL4Bj=8s1vxaOKK+uiCtn_5xpyCpA0j37OUj@mail.gmail.com> <AANLkTi=KsZ3O4_F3cpTzXfoiTC4mqmiLnC1d7qaq0znV@mail.gmail.com> <AANLkTin3LRGjzdwi1_-8=hOdUkOH8__LDVxGHSVEar1y@mail.gmail.com> <BANLkTinsrUXoYv-p3fMGH7jZLTVA8rcfVQ@mail.gmail.com> <BANLkTikzUJvfd=OnTmdGkrHsa7oJtHyaxA@mail.gmail.com> <BANLkTi=-+1U+gxOYaf7jsAoVGARrWCyNyg@mail.gmail.com> <BANLkTimc9oWoiHgaN-rBaVBiYZgb8-=OFg@mail.gmail.com> <BANLkTinXsjUBqV37j+Qn6FRDssvH3UpRnw@mail.gmail.com> <BANLkTin3tjmYNzETuHPbCBYVuk+HdS73YA@mail.gmail.com> <BANLkTimRP9A6rGx2MeDLvnHa02vnOWT_=g@mail.gmail.com> <BANLkTi=g0G_nftcpNZeXG-+qxvT6CHDawQ@mail.gmail.com> <BANLkTincjbDOCwy2hw0aJTAqhEu4eWM-jA@mail.gmail.com> <BANLkTi=a+NdwTO504W_NbRsBHB0vCskqtQ@mail.gmail.com> <BANLkTi=X3MoT=5xqRTxKvLgRms_n4_NihA@mail.gmail.com> <BANLkTinFr7T0XWP3D8R078G-45vYD9_r-w@mail.gmail.com> <BANLkTinneq3CsSc7tWvhQ0Z3oPMEfCvTcQ@mail.gmail.com> <BANLkTinKf8NDDfcJm-HoX9wGcoiVC9z=cg@mail.gmail.com> <BANLkTimmX1acN7hRV_sEAOrL1L6Xg6i8Ow@mail.gmail.com> <BANLkTikJS5jbehmiC_-OaVGMwcPo10LPqg@mail.gmail.com> <BANLkTi=rv8G4eDWzk-YweSgtVO4OZHMpJA@mail.gmail.com> <BANLkTi=LTfXF6xycQv4iYTm319Qbr8OwQQ@mail.gmail.com>
2011/5/17 Felipe Sateler <fsateler@debian.org>:
> On Mon, May 16, 2011 at 09:04, Dan S <danstowell+debmm@gmail.com> wrote:
>> 2011/5/15 Felipe Sateler <fsateler@debian.org>:
>>> On Thu, May 12, 2011 at 06:07, Dan S <danstowell+debmm@gmail.com> wrote:
>>>> 2011/5/11 Felipe Sateler <fsateler@debian.org>:
>>>>> Hi, sorry for taking so long.
>>>>>
>>>>> On Fri, Apr 29, 2011 at 15:57, Dan S <danstowell+debmm@gmail.com> wrote:
>>>>>> 2011/4/16 Felipe Sateler <fsateler@debian.org>:
>>>>>>
>>>>>>> - I would really like to fold all the -dev packages into one. I don't
>>>>>>> see much point in splitting them.
>>>>>>
>>>>>> I've discussed it with the upstream devs and we're OK with merging
>>>>>> them, so I've done that.
>>>>>
>>>>> Good. However, the relationship with thte old packages is wrong. It
>>>>> should Replace the older packages.
>>>>
>>>> Ah right, thanks.
>>>>
>>>>> However, I'm not quite sure if we
>>>>> should apply policy 7.6.1 or 7.6.2 (ie, Replaces+Breaks or
>>>>> Replaces+Conflicts+Provides).
>>>>>
>>>>> What do others think?
>>>>
>>>> In lieu of any other responses (so far), the latter
>>>> (Replaces+Conflicts+Provides) seems to me to have the better
>>>> semantics, although we're not talking about virtual packages (which
>>>> policy 7.5 is pretty specific about). From reading the guide I can't
>>>> decide either; unless anyone can advise, maybe we should go for
>>>> Replaces+Breaks.
>>>
>>> Upon further reading, I think we should use
>>> conflicts+replaces+provides, because we are replacing whole packages.
>>
>> OK, done.
>
> I probably won't be able to dedicate much time to this during this
> week, so if anyone else can have a look at this package and comment on
> it, I'd appreciate it. I'd like to have more eyeballs looking at it
> since it is not a trivial package and I could have missed some things.
I'm very grateful for your help in polishing up this package (indeed,
non-trivial). It would be great if others can comment - anyone?
And if not, what are the next steps?
Thanks
Dan
Reply to: