git-cms-addpkg and new packages

[kpedro88]

I just encountered the following situation:

1. checkout a CMSSW release as usual, call git cms-init
2. create a new package, add & commit files inside the new package
3. call git cms-addpkg to get an existing package

The result is that the tracked files from the new package are removed from the working directory by the sparse checkout that occurs when git cms-addpkg is called. (I had to call git cms-addpkg for the new package to get the files back.)

I'm not immediately sure if there's a way to resolve this problem. Maybe the first time git cms-addpkg is called (identified by the sparse-checkout file having default contents?), it could call git cms-sparse-checkout, similar to what the git cms-[]-topic commands do.

[cmsbuild]

A new Issue was created by @kpedro88 Kevin Pedro.

@Dr15Jones, @dpiparo, @silviodonato, @smuzaffar, @makortel, @qliphy can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here