Missing modules

[redndahead]

The required modules aren't included in the package. views, etc. Also it says it uses feeds and services, but that is not listed as a required module on the install screen. When choosing server I am sure that's why the trekk modules are not enabled.

I think it would be great if this could be released as a drush make file and released here and eventually put on d.o. Any reason why you haven't pursued that?

[tloudon]

hi,

there is a drush make file, it's in the profile/trekk directory. you can run, drush make -y --no-core profiles/trekk/trekk.make from the site root. sorry if this is unclear, it's in the README.md under the installation section.

can you please expand on the problems you are encountering, i'm not sure what you mean by modules not being enabled?

lastly, i don't know if we will ever put this on d.o. i like github's issues, pull requests, and wiki. what major benefits do you think we are missing by hosting it here?

[redndahead]

Doh read instructions.

So download your tarball and run through the installer without using drush. You will see the errors of missing modules. But the dependent modules don't include services so things like trekk_server aren't enabled when you choose server.

Why put it on d.o.? No one ever looks for drupal modules/profiles/themes on github. The only way people will find it is if they see your blog post. I understand that github is nicer as a workflow, but if you want people to use it d.o. is the way to go.

Also using that make file I can't download your trekk modules. So it's pretty much download this tar and then run drush make to download the rest. Which is a non-starter for me. I would either break out those modules in separate github repos or put them on d.o. If you want an example of how I prefer to separate modules in distros you can look at http://github.com/amoore5 and https://github.com/amoore5/campuscms-profile for the install profile.

Where I currently work we are looking for a good way to share content across our sites so I am interested in this project, but it would be hard to build our sites in it's current form.

[tloudon]

@cmjns can you please take a peek @ the dependencies in the installer and trekk_server?

@redndahead the workflow is very important to us. pressflow did pretty well on launchpad, so I'm hopeful things will work well on github. the distribution is brand new, so we're still figuring some things out in terms of optimal setup. I appreciate your willingness to try it out and to make suggestions! I'll look at the repo mentioned to see if it would fit our needs.

Cheers

[redndahead]

remember pressflow had no choice but to put it somewhere else because of the type of distro they were building (hacking core). With the improved packaging on d.o. they wouldn't have to put it someplace else now. I guess the main thing for me is split out the custom modules into separate repos. Then I can include it in my .make file.

[cmjns]

@tloudon the trekk_server module shouldn't depend on anything more than services (v3), which has it's own deps and doesn't do anything with out a server. The README.md notes this, and notes that we recommend using rest_server. I think this is not an issue with dependencies in the .info but with how we've packaged it.

[tloudon]

@cmjns thanks, I'll look over the info files.