search

archlinux / asp

Arch Build Source Management Tool
MIT License
294 stars 34 forks source link

Split packages -- Feature or bug? #8

Closed thiagowfx closed 7 years ago

thiagowfx commented 10 years ago

Today I just tried to do a 

asp export gvim-python3

However, this outputs:

error: unknown package: gvim-python3

But

asp export vim

works okay. Now, the PKGBUILD of vim contains:

pkgbase=vim
pkgname=('vim-minimal' 'vim' 'vim-python3' 'gvim' 'gvim-python3' 'vim-runtime')

So you see the issue: asp only recognizes pkgbase. Now, it would be nice to be able to export other packages from package name.

Did you keep asp this way to be simple (feature) or it should have been able to export gvim-python3 (bug)?

plitter commented 9 years ago

I think this happens because this is how they build the package for us. When you download the package it has already been compiled according to the rules here. asp and abs only provides us with the recipee to build the packages. You can however change your PKGBUILD locally and then when the next version comes just update your local repos and fix merge conflicts (at least this is what I'm gonna try, first time for me using git with an actual project :P ) One thing about the vim recipee is that you most likely only want one of the versions (vim-minimal, vim, vim-python3, ...) and your wasting a lot of time building them all.

falconindy commented 9 years ago

Sorry, thought I had replied to this. I'm interested in a solution to this problem, but intentionally left it out as a v1 feature. Ideally, Archweb would allow resolution of packages back to their pkgbase. Due to the sparse nature of asp, it simply isn't feasible to implement it directly in asp.

progandy commented 9 years ago

It should be possible with archweb: