After adopting alacconvert and libalac, I decided that they should be handled as one (split) pkg, so if someone could please merge:
alacconvert: https://aur.archlinux.org/packages.php?ID=53497
libalac: https://aur.archlinux.org/packages.php?ID=53480

into
alac: https://aur.archlinux.org/packages.php?ID=59613

On Tue, 29 May 2012 16:25:48 -0400
SJ_UnderWater <webmaster0007@rcn.com> wrote:

> After adopting alacconvert and libalac, I decided that they should be handled as one (split) pkg, so if someone could please merge:
> alacconvert: https://aur.archlinux.org/packages.php?ID=53497
> libalac: https://aur.archlinux.org/packages.php?ID=53480
>
> into
> alac: https://aur.archlinux.org/packages.php?ID=59613

It sounds reasonable, btw you may better upload an alac-svn package
instead, since there is still no release and your package actually
uses svn.

Also using a split package is probably not strictly necessary.
A single alac (that provides both libalac and alacconvert) would be
sufficient, since it will not result a big one and upstream does not
split or suggest to split.

Otherwise, if in future upstream will provide two separate source tarball for
releases, splitting again will be necessary.

So, please re-upload a new alac-svn (that provides alac, libalac{,-svn} and
alacconvert{,-svn}), and I'll proceed by deleting alac and merging libalac
and alacconvert into alac-svn.

Thanks


- speps -

Done, see: https://aur.archlinux.org/packages.php?ID=59618

On May 29, 2012, at 8:43 PM, speps wrote:

> On Tue, 29 May 2012 16:25:48 -0400
> SJ_UnderWater <webmaster0007@rcn.com> wrote:
>
>> After adopting alacconvert and libalac, I decided that they should be handled as one (split) pkg, so if someone could please merge:
>> alacconvert: https://aur.archlinux.org/packages.php?ID=53497
>> libalac: https://aur.archlinux.org/packages.php?ID=53480
>>
>> into
>> alac: https://aur.archlinux.org/packages.php?ID=59613
>
> It sounds reasonable, btw you may better upload an alac-svn package
> instead, since there is still no release and your package actually
> uses svn.
>
> Also using a split package is probably not strictly necessary.
> A single alac (that provides both libalac and alacconvert) would be
> sufficient, since it will not result a big one and upstream does not
> split or suggest to split.
>
> Otherwise, if in future upstream will provide two separate source tarball for
> releases, splitting again will be necessary.
>
> So, please re-upload a new alac-svn (that provides alac, libalac{,-svn} and
> alacconvert{,-svn}), and I'll proceed by deleting alac and merging libalac
> and alacconvert into alac-svn.
>
> Thanks
>
>
> - speps -

On Tue, 29 May 2012 21:00:22 -0400
SJ_UnderWater <webmaster0007@rcn.com> wrote:

> Done, see: https://aur.archlinux.org/packages.php?ID=59618
>
> On May 29, 2012, at 8:43 PM, speps wrote:
>
> > On Tue, 29 May 2012 16:25:48 -0400
> > SJ_UnderWater <webmaster0007@rcn.com> wrote:
> >
> >> After adopting alacconvert and libalac, I decided that they should be handled as one (split) pkg, so if someone could please merge:
> >> alacconvert: https://aur.archlinux.org/packages.php?ID=53497
> >> libalac: https://aur.archlinux.org/packages.php?ID=53480
> >>
> >> into
> >> alac: https://aur.archlinux.org/packages.php?ID=59613
> >
> > It sounds reasonable, btw you may better upload an alac-svn package
> > instead, since there is still no release and your package actually
> > uses svn.
> >
> > Also using a split package is probably not strictly necessary.
> > A single alac (that provides both libalac and alacconvert) would be
> > sufficient, since it will not result a big one and upstream does not
> > split or suggest to split.
> >
> > Otherwise, if in future upstream will provide two separate source tarball for
> > releases, splitting again will be necessary.
> >
> > So, please re-upload a new alac-svn (that provides alac, libalac{,-svn} and
> > alacconvert{,-svn}), and I'll proceed by deleting alac and merging libalac
> > and alacconvert into alac-svn.
> >
> > Thanks
> >
> >
> > - speps -
>

Done, thanks.

Btw you may better add provides and conflicts lines for continuity; like

provides=('alac' {libalac,alacconvert}{,-svn})
conflicts=(${provides[@]})
replaces=(${provides[@]:1})

Also please do not top post, cheers.

- speps -