Quoting Ralph Giles (2017-11-04 18:50:07) > On 2017-11-04 3:51 AM, Jonas Smedegaard wrote: >> I believe that from your own rule, stuff generated during build by >> upstream build tools - typically but not necessarily listed in >> upstream .gitignore - should hot be installed either. > > Unfortunately, `cargo package` includes everything in the working > directory that's not in .gitignore or explicitly excluded by > Cargo.toml. so there are many .crate packages containing unnecessary > cruft. > > If the idea is to provide a local replacement for the upstream > crates.io repository, then the important thing is that the contents of > the .crate packages match, so the contents hash the same and builds > are reproducible.
Thanks for that additional information. I believe this is exactly what we intend to do here (but I am new aboard, so don't lean too much on my input). > You didn't cite a particular crate which is including .pc files, but > filing a bug with upstream to exclude them in Cargo.toml would be the > best way to address that. You snipped the parted clarifying that the .pc came not from upstream but was created during my Debian package build: > The ".pc" directory, created during build by a packaging helper tool, > should certainly not be installed. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private