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

"Scanning entire ports tree" - why? #211

Open
rwv37 opened this issue Dec 30, 2022 · 2 comments
Open

"Scanning entire ports tree" - why? #211

rwv37 opened this issue Dec 30, 2022 · 2 comments

Comments

@rwv37
Copy link

rwv37 commented Dec 30, 2022

This is not really an "issue", but a question:

When you do a synth status, it says "Scanning entire ports tree". This step takes a long time (at least for me). So I can't help but wonder: Why does it need to scan the entire ports tree? Why can't it instead just scan the subset implied by the packages in question?

@jrmarino
Copy link
Owner

Yes it's necessary to do the entire tree -- this requirement came after flavors was introduced.
The FreebSD ports projects needs to provide a suitable index for every change of the ports tree, but they do not. This is a major failure in my opinion.

The absurd length of time is because of 1) limitations of the makefile system and 2) unchecked abuse of the makefile system with regard to file inclusion and real-time evaluation of command output. Since I left the project, nobody checks for these things.

If the index were generated externally, all users could use it instead of having to generate one themselves.

@rwv37
Copy link
Author

rwv37 commented Dec 31, 2022

Thanks. If it's not a hassle, could you please point me to a source where I can learn more detail about this situation, if you know of one?

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