Skip to content

Commit

Permalink
Removed ding_bookmark.
Browse files Browse the repository at this point in the history 
The repo does not seem to be available any more.
  • Loading branch information
@kasperg
kasperg committed Mar 23, 2012
1 parent 9b939f3 commit 2b4b04c
Showing 1 changed file with 0 additions and 1 deletion.
1 change: 0 additions & 1 deletion ding_user_frontend.info
View file
Expand Up @@ -5,7 +5,6 @@ dependencies[] = "date_popup"
dependencies[] = "ding_debt"
dependencies[] = "ding_loan"
dependencies[] = "ding_reservation"
dependencies[] = "ding_bookmark"
dependencies[] = "features"
dependencies[] = "i18n_field"
dependencies[] = "list"
Expand Down

3 comments on commit 2b4b04c

@bibchi
Copy link

@bibchi bibchi commented on 2b4b04c Apr 3, 2012

Choose a reason for hiding this comment

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

ding2.make misses ding_bookmark because it use ding_user_frontend tag 7.x-0.26

@CheMical
Copy link
Contributor

Choose a reason for hiding this comment

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

ding_bookmark is at the moment available at https://github.com/dingproject/ding_bookmark though it should be moved to the Ding2 organization to make things work correctly when using Drush make.

Only core team can make this change.

A workaround would be to add ding_bookmark as a module with correct url in the make file in your profile repository:

projects[ding_bookmark][type] = "module"
projects[ding_bookmark][download][type] = "git"
projects[ding_bookmark][download][url] = "git@github.com:dingproject/ding_bookmark.git"
projects[ding_bookmark][download][tag] = "7.x-0.5"

If you don't have your own profile repository then fork ding2.

@kasperg
Copy link
Member Author

Choose a reason for hiding this comment

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

I've transfered ding_bookmark back to ding2 and readded the module to make files and dependencies here 4075eb8 and 927e829.

Please sign in to comment.