On Thu, Jan 16, 2014 at 11:46:12PM +0000, Jerome Leclanche wrote: > On Thu, Jan 16, 2014 at 11:31 PM, Dave Reisner <[email protected]> wrote: > > On Thu, Jan 16, 2014 at 08:52:46PM +0100, Lukas Fleischer wrote: > >> On Tue, 14 Jan 2014 at 23:54:28, Dave Reisner wrote: > >> > On Tue, Jan 14, 2014 at 11:12:17PM +0100, Lukas Fleischer wrote: > >> > [...] > >> > > * Test your utility. Do some manual tests and automated tests you > >> > > described below. Fix common use cases. > >> > > > >> > > * Create a package that contains mkaurball and put that in [extra] or > >> > > [community]. Update all Wiki articles etc., replacing `makepkg > >> > > --source` with `mkaurball`. > >> > > >> > I think you're missing a few steps here. For starters, I don't believe > >> > the current .AURINFO parser is capable of consuming the format I'm > >> > advertising. Including it without changing the AUR's parser means... > >> > Refused uploads? Bad data displayed? > >> > >> I didn't read code or test your tool before I wrote the mail, so I > >> didn't know that you > > > > Fair enough... I assumed when I mentioned split packages and referenced > > Allan's post that it was understood I was going outside of the current > > .AURINFO format (which is far too simplistic to be of value in the long > > term). > > Do you have some example .AURINFO files you can post to the list? I've been > dealing with domain-specific packaging a lot the past month and I'm > very interested in a potential solution to all this.
Clone my repo and run './reflect /path/to/PKGBUILD'. If you have an ABS tree cloned into /var/abs, you can just run './reflect $repo/$pkg'.
