Skip to content
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

Improve handling of git packages #812

Open
fosskers opened this issue Aug 15, 2023 Discussed in #811 · 3 comments
Open

Improve handling of git packages #812

fosskers opened this issue Aug 15, 2023 Discussed in #811 · 3 comments

Comments

@fosskers
Copy link
Owner

Discussed in #811

Originally posted by sonicbhoc August 15, 2023
So one thing that I've noticed is that I have to constantly tell Aura for each package that I don't want to view diffs for the build files. On top of this, there doesn't seem to be a way to automatically skip packages that haven't changed their build files. I'd love to see options to configure these (and if they are there, I don't know how I missed them).

Finally, I noticed that some packages fail when copying files or when the build uses cmake due to path issues. I'm not sure exactly what causes these failures.

The packages that failed include:

  • ofono-git
  • uavs3d-git
  • bluez-tools-git
@fosskers
Copy link
Owner Author

@sonicbhoc Thank you for reporting! Are you using Aura 3 or Aura 4 when trying to build these?

@sonicbhoc
Copy link

Aura 4.

Also, I was going to mention that the incessant nagging for viewing the diffs was indeed a configuration option I accidentally enabled in the config toml file. Oops.

That being said, the rest of them are real issues. I'd love to be able to tell aura to skip building git packages if the build files didn't actually change after a pull. makepkg does it this way iirc; I don't recall it rebuilding things if nothing changed. I imagine such a feature could be added as something in the toml config file that can also be overridden with a command-line switch if necessary.

Lastly, the list of packages I encountered issues with (you can add bluez-git to the list, but bluez-alsa-git surprisingly works just fine) all seem to fail if the build has to do something with pathing or the local build directory somehow. Copying files and CMake list file failures seem to be common. When I get home I can paste the output from Aura for you. Thanks!

@fosskers
Copy link
Owner Author

makepkg does it this way iirc

Aura is calling makepkg internally, so this may be due to passing the --force flag that's making it do a build no matter what.

When I get home I can paste the output from Aura for you.

Yes this would be helpful, thanks! I will also try building on my own machine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants