Port was copied with svn copy and modified to fix some problems.
Commit message:
Added port textproc/rubygem-html-pipeline required for gitlab 10.8.5.
Details
Details
- Reviewers
tz swills - Commits
- rP473552: Updated to 2.7.1 which is required for gitlab 10.8.5.
All is build using poudriere and tested.
Diff Detail
Diff Detail
- Repository
- rP FreeBSD ports repository
- Lint
Lint Skipped - Unit
Tests Skipped
Event Timeline
Comment Actions
Why not downgrading rubygem-html-pipeline27 to 2.7.1 since it is exactly only for GitLab to run?
Comment Actions
I'd say it is a sunpoet always upgrading everything problem.
Maybe the dependencies added specifically for gitlab should be marked as special, say, with a specific PKGNAMEPREFIX. And always have a PORTSCOUT=ignore or with so that they do not show up in any report as being outdated.
What if they all had PKGNAMEPREFIX=rubygem-gitlab-? or a PKGNAMESUFFIX=-gitlab?
Comment Actions
Sunpoet is doint a really good job it he saves me a lot of work.
The port was not broken by sunpoet but is wrongly defined by the gitlab team.
I prefer more to have a specific port for version 2.7.1 as this will maybe be fixed in gitlab already with the next version.
But I found another port called textproc/rubygem-html-pipeline-gitlab so I updated it to version 2.7.1 and will use this.
Can you please have a look to the new diff?
Comment Actions
I do not like this. A 27 suffix tells every port maintainer to have 2.7.x where x is the highest number.
The risk is very high it even myself will update this port in my next update cycle to the highest x.
That is the reason why I personally prefer 271 as suffix to make absolutely clear that this port is fixed to 2.7.1 and no update it allowed.