[tur-users] Unstable (AKA -{svn, cvs, devel}) packages in [community] ?

[Varun Acharya]

Callan Barrett wrote:
> On 4/15/07, Chris Mortimore <chris.mortimore at googlemail.com> wrote:
>   
>> Set up a [community-unstable] repo?
>>     
>
> What for? That and a community-testing repo just seems like extra
> complication. Where's the document that says [community] is strictly
> for non-development software?
>
>   
Unstable creates a small problem for the x86_64 port..Were usually 
behind i686 when it comes to community because were extremely short 
handed right now, and so we update packages at a later date. This is ok 
for stable releases but when it comes to svn, it seems quite silly to 
just 'makepkg' on the i686 PKGBUILD, considering that the PKGBUILD might 
be quite old in terms of -svn releases. When xfce-svn(for example) was 
in unstable, the usual process was to update all svn packages with 
versionpkg after which the i686 maintainer would look into it whenever 
he felt necessary and run versionpkg for his architecture. End result: 
pkgversion will be changed. The problem here is some TU's don't like 
their PKGBUILDs being touched, and I can understand how a change like 
pkgversion in the PKGBUILD can be quite annoying and confusing. This 
will of course be solved with whatever new SCM we choose to seperate the 
architectures, but how do we handle this issue for now.

 In a nutshell: The x86_64 project,for now atleast, has to run 
versionpkg on -svn/-git/-cvs PKGBUILDs. The changes will all be tagged 
CURRENT-64 as usual. Do the maintainers of -svn/-cvs/-git have any 
objections to this ?


-Varun