Re: [orca-list] [solved] Re: Arch+orca stopped talking to me

[Peter Vágner <pvdeejay gmail com>]

Hello,
As for conflicts and stuff, there might be packages such as orca-testing 
or orca-unstable.
There is a keyword provides and replaces within PKGBUILD script where 
you can specify that this package is in conflict with the other version 
of the same software.
I havent read arch packaging guidelines however I have recognized these 
in several scripts.


Greetings

Peter

On 12.03.2013 18:52, Kyle wrote:
> That would be great. I don't think there would be a problem cleaning 
> them up if needed and uploading them to AUR so that people can test 
> the latest released accessibility stack. I also need to check to see 
> whether or not there is an actual qt-at-spi release, or if we're just 
> supposed to keep using git, especially since qt5 is now available, and 
> from what I read, it's supposed to communicate with at-spi2 by default.
>
> At this point, I need to consider how these packages are to be named 
> in AUR. For example, simply giving the AUR versions that are the 
> latest releases the same names as the official packages could cause 
> conflicts for people who do not wish to upgrade their accessibility 
> stack, but this could only be my perception of a problem that doesn't 
> really exist. I'll look at the AUR packaging guidelines and go from 
> there. If that doesn't work, there's always the possibility of 
> providing my own accessibility-testing repo for pacman, which could be 
> added to /etc/pacman.conf if desired.
> ~Kyle
> http://kyle.tk/