See $Summary.
Created attachment 315313 [details, diff] ebuild patch Changes: - Split vim files in puppet-syntax package (to be attached), bug 417085 - newer dev-ruby/ruby-ldap is ruby 1.9 compatible. Since this was the only blocker I updated puppet to 1.9 and it seems fine Questions: - I saw that you use some redhat files (since they are newer) and some custom ones instead of conf/gentoo from the puppet tarball. Would it make sense to push those files in the upstream tarball? - you have a bunch of commented deps, why is that?
Created attachment 315315 [details] app-vim/puppet-syntax-2.7.14 New puppet-syntax ebuild. I took the vim syntax files from the puppet tarball and put them in a new tarball, in order to be able to use app-vim eclass, like in the other *-syntax ebuilds
Is the puppet-module-tool shipping with 2.7.14? Here they state that it should already be in 2.7.13 but it isn't for me. https://github.com/puppetlabs/puppet-module-tool#readme
(In reply to comment #3) > Is the puppet-module-tool shipping with 2.7.14? > > Here they state that it should already be in 2.7.13 but it isn't for me. > https://github.com/puppetlabs/puppet-module-tool#readme https://github.com/puppetlabs/puppet-module-tool/blob/master/README.markdown#important-note-module-merged-into-core-puppet
hi. sorry for delay. Could you tell me why should it separate ebuilds for puppet-syntax? it is enough to use vim-syntax USE flag, isn't it?
Yeah, vim-syntax.. I guess it is just a typo.
Darn.. Sorry, I didn't read the entire comment :P
As I said in bug 417085 vim-syntax should be a separate package because I have puppet manifests in a git repo, and I need the syntax file without having to install the whole puppet package.
Theo, can you please file a new bug for the remaining things?
