Gathering "package" tags and putting the same "package" tag in several releases?

[Martin-Grunewald]

Hi,

I have a question how to most effectively organise the collection of several "package" tags, given that in GIT package tags in the cvs language do not exist as always the full repository is tagged.

In the CVS language, say I have a few new tags of some packages which I want to test together. So I make a release area, and then need to pull in each updated package from someone else's GitHub repository. How does that work if the tags are repository wide? How do I ensure I get from each GiutHub repository only the single/few package I really want?

Related question: in the CVS world it was possible to have a single package tag in several release series (eg, the same HLTrigger/Configuration tag in both 53X and 61X). How does GIT support this, given that tags are not per package? Would I need to develop in one branch and then copy and commit for the other branches, given that "tags" are repository wide?

[Martin-Grunewald]

IOW, using git cms-addpkg, is there a way to specify from which (personal) github repository / branch / tag to get the package? BTW, where do I find the documentation of cms-addpkg? The current help text does not say this:

gruen@ughent2:/CMS3/CMSSW_6_2_0_pre8/src/[126]$ git cms-addpkg --help
No manual entry for git-cms-addpkg
gruen@ughent2:/CMS3/CMSSW_6_2_0_pre8/src/[127]$ git cms-addpkg -h
git cms-addpkg [options] SubSystem/Package

Options:
-h this help message

-d, --debug enable debug output
-f, --force force dangerous operations
--https use https, rather than ssh to access your personal repository
-q, --quiet do not print out progress
-y, --yes assume yes to all questions

[ktf]

No, at the moment, you'll need to use git remote add and git pull to add a different repository and merge your changes. Alternatively you can use git-cms-merge-topic, but that will require the topic being published, kinda like `cmstc tagset -a . I'll comment in a separate thread about the help.

[Martin-Grunewald]

Hmm, but how do I specify the individual package I want the updates from, given that I do not want the all repository changes to be pulled in every time?

[davidlt]

Use sparse checkout, e.g: http://jasonkarns.com/blog/subdirectory-checkouts-with-git-sparse-checkout/

[Martin-Grunewald]

As one of the people commented there, this is rather cumbersome (editing config files for each separate case)
and hence can't be put in a script (eg, the use case is that I grab several tags [packages] from different personal
repos). Hence I'd like to ask that cms-addpkg gets empowered to take a repository/branch/tag as an additional argument where to grab things from.... could that be foreseen, please?

[DAMason]

Will chime in here since this is relevant to a question I was trying to understand. If this is too old & forgotten I'll open a new issue if nobody sees this :)

So there is the CMSSW development use case which is referred to in the FAQ and here, but there is the probably more common CMSSW analysis use case, where typically an analyzer is pulling in tags from different releases to catch the latest PATtuple recipe, pull in analysis code not tied to a specific release, etc. Quite often we have a dozen-odd packages, each from a different release or standalone tag. To be more specific, how might I do something like:

cvs co -r cms538_v1 -d SusyAnalysis/SusyNtuplizer UserCode/LPCPJM/SusyAnalysis/SusyNtuplizer
cvs co -r V00-00-13 RecoMET/METFilters
cvs co -r V00-00-08 RecoMET/METAnalyzers
cvs co -r V00-11-17 DPGAnalysis/SiStripTools
cvs co -r V00-00-30-01 -d EGamma/EGammaAnalysisTools UserCode/EGamma/EGammaAnalysisTools
cvs co -r V15-01-11 RecoParticleFlow/PFProducer/python
cvs co -r V05-11-02 RecoJets/JetProducers
cvs up -r CMSSW_5_3_8_patch3 RecoJets/JetProducers/interface/JetSpecific.h
cvs up -r CMSSW_5_3_8_patch3 RecoJets/JetProducers/src/JetSpecific.cc
cvs up -r CMSSW_5_3_8_patch3 RecoJets/JetProducers/plugins/CATopJetProducer.h
cvs up -r CMSSW_5_3_8_patch3 RecoJets/JetProducers/plugins/CATopJetProducer.cc
cvs co -r V05-00-16 DataFormats/JetReco
cvs co -r regressionMay18a RecoEgamma/EgammaTools
cvs co -r V00-02-15 DataFormats/StdDictionaries
cvs co -r v1-2-3 -d QuarkGluonTagger/EightTeV UserCode/tomc/QuarkGluonTagger/EightTeV

(The first line is covered now since we moved that guy to GitHub on its own, but the remaining 14 or so lines has me worried...)

Thanks,

--Dave

[davidlt]

@DAMason, frankly that looks like a mess. It's better to create a branch/repo for your recipe. Instead of doing all this, then I would need just to pull some branch/tag.

[ktf]

As long as your changes are in a release or in the HEAD, you can now follow what described in:

http://cms-sw.github.io/cmssw/advanced-usage.html#i_need_to_checkout_a_file_from_the_old_cvs_head__a_release_tag_how_can_i_do_it

[Martin-Grunewald]

Sorry, but concerning the comment by davidlt: "create a branch/repo"
how do you do that? it seems to me that this is what was asked for in the first place,
IOW if we knew how to get a repo with those tags, then the problem is solved (ie, we
would just clone that repo). So how does one make a rep with excatly a specified list of tags
on top of a base release?

[ktf]

@DAMason @Martin-Grunewald can you see if:

#10 (comment)

gives you an idea on how to solve such a usecase in the git way (look at the second part, the first one is for the trivial case).

[Martin-Grunewald]

Hi,

I do not understand your reply here: the "#10" link refers to DAMAson's comments further up in the thread,
so how should that be a solution?