Hey all!

As Drush is now available in the debian repository, i wanted to ask if someone knows / wants to make a yum drush package. If drush would be in the repos of centos/fedora/redhat, this would be fantastic!
I'm a total noob in this stuff, but if i can help out with something, i'm available....

greetings,
tom

Comments

pescetti’s picture

pescetti commented

subscribing

junedkazi’s picture

junedkazi commented

subscribing

moshe weitzman’s picture

moshe weitzman commented

I believe that David Strauss has started this. Check started Macports, and anarcat did debian. fyi.

KrisBuytaert’s picture

KrisBuytaert commented

Moshe any updates on that ? Or pointers to what David has done so far ?

david strauss’s picture

david strauss
he/him
commented

I currently maintain a Yum repository at yum.fourkitchens.com. If my packages are out of date or somehow needing love, I'm happy to fix things.

dakku’s picture

dakku commented

++

kenorb’s picture

kenorb commented

No package drush available.
Nothing to do
--
CentOS release 5.6 (Final)

kenorb’s picture

kenorb commented

1. Create repo file

$ sudo vim /etc/yum.repos.d/fourkitchens.repo

See content: https://wiki.fourkitchens.com/display/TECH/Using+the+Four+Kitchens+Yum+r...

2.

$ sudo yum update

3.

$ sudo yum install drush
kenorb’s picture

kenorb commented
Status: Active » Fixed
kenorb’s picture

kenorb commented
Status: Fixed » Active

It's fixed? Or drush-2-3.noarch is too old?

greg.1.anderson’s picture

greg.1.anderson commented

Drush-2 is deprecated,, drush-3 is supported for critical bugfixes only (or unsupported now?), drush-4 is best.

karolacello’s picture

karolacello commented

Information on https://wiki.fourkitchens.com/display/TECH/Using+the+Four+Kitchens+Yum+r...
is outdated now:

http://yum.fourkitchens.com/pub/centos/5/noarch/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: fourkitchens-centos5-noarch. Please verify its path and try again
greg.1.anderson’s picture

greg.1.anderson commented

Now Drush-5 is the recommended release, and PEAR is the best way to get it. See the Drush project page.

siwinski’s picture

siwinski commented

I am a Fedora packager and I am working on this package. There is already a "drupal6-drush" package (v4.1) for Fedora, but I have started talking to that package maintainer (we work at the same company) about creating a generic drush package (using PEAR install) since that package is out of date, categorized as Drupal 6 (instead of 6, 7, and usually 8), and uses a manual (i.e. not PEAR) install. I will update this issue when any progress has been made.

greg.1.anderson’s picture

greg.1.anderson commented

Since Drush 5-x is out, it would be best to categorize Drush-4.x as "Drupal 5", and Drush-5.x as "Drupal 6, 7 and usually 8". Note that Drush-5.x does not support Drupal 5, but Drush 4.x does.

siwinski’s picture

siwinski commented

Fedora/EPEL update: Drush PEAR-based package is now available for Fedora 18+ and EPEL 6+ (RHEL/CentOS/Scientific Linux/etc.). Currently version 5.8.0 is available in the repos and version 5.9.0 was just submitted for testing today. You can install the package on a supported system by running "sudo yum install php-drush-drush" (Fedora enforced "php-shortchannel-pkg" package name). Note that the package also virtually provides drupal6-drush and drupal7-drush so you could yum install the pkg by those names as well.

For Fedora/EPEL pkg issues or requests, please file a bug at: https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=php-drush-drush

greg.1.anderson’s picture

greg.1.anderson commented
Version: All-Versions-2.0 » 8.x-6.x-dev
Status: Active » Closed (won't fix)
Issue tags: +Needs migration

This issue was marked closed (won't fix) because Drush has moved to Github.

If this feature is still desired, you may copy it to our Github project. For best results, create a Pull Request that has been updated for the master branch. Post a link here to the PR, and please also change the status of this issue to closed (duplicate).

Please ask support questions on Drupal Answers.