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

add linter for noarch #134

Merged
merged 3 commits into from
Jun 12, 2017
Merged

add linter for noarch #134

merged 3 commits into from
Jun 12, 2017

Conversation

daler
Copy link
Member

@daler daler commented Jun 12, 2017

@johanneskoester @bgruening anything else you can think of to look for in the linter?

('python' in deps) and
not _has_preprocessing_selector(meta)
) and (
'noarch' not in meta['build']
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does above line also work if meta has no build section?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks, fixed

if (
('gcc' not in deps) and
('python' in deps) and
not _has_preprocessing_selector(meta)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the point of the preprocessing selector? Is it just because we cannot be sure in that case?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right. I was thinking if there was something strange enough in the recipe that it needs preprocessing selectors then it's not a good candidate for noarch.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds reasonable.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm worried that this disables the linter for too many packages. I think there are a few packages with pre-processing selectors in the url section or test section - still we would like to have noarch packages for it. Just a feeling, not sure how often these cases are.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry didn't get a chance to reply before -- If there's a pre-processing selector in the url or test section, doesn't that mean it's arch-specific?

Either way I think it's ok at least for now to let some packages slide until we get a better feel for what works with noarch, and then tighten up the linter later.

@bgruening bgruening merged commit 574a551 into master Jun 12, 2017
@bgruening bgruening deleted the noarch-lint branch June 12, 2017 19:52
@bgruening
Copy link
Member

Thanks @daler!

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

Successfully merging this pull request may close these issues.

None yet

3 participants