-
Notifications
You must be signed in to change notification settings - Fork 12
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
Feature Request: add option to easily use local package #4
Comments
Does this do anything that local repos don't already do? |
It would be much easier to use. |
I would also like the ability to have this, in some form or another. A couple of times i have been trying to package something that depends on a package than isn't in solus' repos. Therefore to actually build the package I wanted to in the first place I need to package and submit the dependency, wait and see if it gets accepted before I can finally package the application I wanted to in the first place barring some ugly shenanigans I have to do in the chroot enviroment. In my mind I should be able to run solbuild index and then add any local packages to my builddeps |
..We support local repos. Check the profile files in this repo and the manpages :P |
Woah, apparently i'm dumb, that helps a lot. 🤦♂️ |
xD happens :P maybe i could set up some tutorials for this |
Local repos have now been simplified greatly and documented for very easy use and integration with the current tooling. This configuration package will be available to install and use after the next package sync in Solus https://solus-project.com/articles/packaging/local-repository/en/ |
I would like to propose an enhancement : first check the local repository and if the package is not there get it from the Solus repository. This would be more convenient. |
@kyrios123 Have you tried the local repo as documented above? That's what it does... |
@sunnyflunk of course! It looks to me that a nice enhancement would be to give the priority to the packages in the local repository and take the missing ones from the Solus repository, so in this particular cases, I would have just to copy the ffmpeg package in my local repo perform my tests and then purge my local repo. There could be warning messages to indicate for each missing package that it's downloaded from the remote repository. I don't think it's complex to implement and it would make Solbuild even more user friendly but of course it's just a nice to have. Just a suggestion for a future update. |
@kyrios123 To me you have described how it currently works. You would put ffmpeg in /var/lib/solbuild/local run I suggest you try to find me on IRC if yours is not working that way so can work through it. |
@sunnyflunk this is what I tried to do first, but it didn't work. |
@kyrios123 ok, can you remove everything from the local repo except the ffmpeg and ffmpeg-devel eopkgs and reproduce vlc failing to build? Confirm This is what it should be doing from a quick build of vlc (but I used libflac as it was quick).
|
Okay sorry, my mistake! |
I say we replace all these options by releasing ferryd into Solus :D |
Something like:
sudo solbuild build --replace-pkg "pkgname:path/to/pkg.eopkg"
.This would make it easier to try how two packages interacts.
The text was updated successfully, but these errors were encountered: