New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pkg_* tools repo stack is broken #23
Comments
I see that |
xzhayon
pushed a commit
to xzhayon/portbuilder
that referenced
this issue
Nov 5, 2012
pkg_* tools have no idea of remote repository, avoid checking if the package is available; pkg.fetch() will fail, if it is not. This commit fixes DragonSA#23.
xzhayon
pushed a commit
to xzhayon/portbuilder
that referenced
this issue
Nov 5, 2012
pkg_* tools have no idea of remote repository, avoid checking if the package is available; pkg.fetch() will fail, if it is not. This commit fixes DragonSA#23.
xzhayon
pushed a commit
to xzhayon/portbuilder
that referenced
this issue
Nov 5, 2012
This commit references DragonSA#23.
xzhayon
pushed a commit
to xzhayon/portbuilder
that referenced
this issue
Nov 5, 2012
With pkgng, instead, it's better to trash the package if we're not sure it's OK. This commit references DragonSA#23.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
pkg.info(repo=True)
doesn't work with pkg_* tools, so the whole repo stack isn't even started. Additionally,pkg.add(repo=True)
callspkg_add -r $pkgname
, butpkg_add -r
needsLATEST_LINK
. The former can be fixed making theRepo
stage returnTrue
when using pkg_* (an abstract method should be created for this, likepkg.exists()
or similar), the latter by using theRepoFetch
stage.This is not high priority, in my opinion.
The text was updated successfully, but these errors were encountered: