search

galaxyproject / galaxy

Data intensive science for everyone.
https://galaxyproject.org
Other
1.42k stars 1.01k forks source link

The 'successor' concept for TS repos #606

Open martenson opened 9 years ago

martenson commented 9 years ago

Could you guys spec it out a little bit more? What do you expect of it and how it should behave. @bgruening @nsoranzo @erasche

xref: https://github.com/galaxyproject/tools-iuc/pull/249

hexylena commented 9 years ago

Hmm. I'd see it as a "final" push to a repository, where you'd push a single file that looks like:

<deprecation>
  <successor name="bowtie2" owner="iuc"  changeset="auto-filled-in" toolshed="auto-filled-in"/>
  <reason>
This repository was deprecated due to the much better wrapper of bowtie produced by the IUC.
  </reason>
</deprecation>

something simple like that?

bgruening commented 9 years ago

@erasche like it. Not sure if this needs to be pushable, but these information needs to be entered into the TS, somehow. Tool updates should read this information and follow along to get the new version under different user name.

The most complicated part is probably to get the Tool linage correct, because it needs now to track different owners, repository names.

nsoranzo commented 9 years ago

I agree with @bgruening: it does not need to be a final commit and Galaxy should automatically let the user move to the other-user-repository as in normal repo upgrades.

hexylena commented 9 years ago

(my suggestion of a final commit is based around my hopeful view that 100% of repository maintenance will be automated and part of git history, like we did with repository metadata in the additional .shed.yml keys. Please don't make me login to the TS...

tir. 18. aug. 2015, 19.31 skrev Nicola Soranzo notifications@github.com:

I agree with @bgruening https://github.com/bgruening: it does not need to be a final commit and Galaxy should automatically let the user move to the other-user-repository as in normal repo upgrades.

— Reply to this email directly or view it on GitHub https://github.com/galaxyproject/galaxy/issues/606#issuecomment-132310100 .

nsoranzo commented 9 years ago

@erasche: I was indeed thinking that we can added 2 new fields to .shed.yml:

These will be tracked in the Tool Shed database (and also in our git repository for tools-iuc and tools-devteam), but not in the Mercurial Tool Shed repository.

hexylena commented 9 years ago

@nsoranzo ah! Okay, that's fine then. Yes, agreed, it doesn't need to be tracked by mercurial. Just as long as we're tracking it in git/planemo is handling it. My apologies for the miscommunication here.