Mickey
Mickey
Now that we switched to Path::Tiny, we can use its digest methods to produce the checksums (less dependencies?)
We don't keep permissions history and we could store the release's modules permissions at the time of indexing as we have that info available (new type). This will be helpful...
`ElasticSearchX::Model` is not completely made compatible with `ES 2.x` and some of its functionality is redundant (scrollers, bulk) as we can use the underlying `Search::Elasticsearch` module directly. Removing it will...
When indexing a release with '--status latest', make sure we don't end up with multiple releases of the same distribution with 'status=latest', this can happen when we force the status...
(for Perl) in `manage` I'd like to be able to check whether a source in the repo is patched (compare digest with upstream) and display the patch content in case...
in `phase I` we build half-baked toolchain modules that depend on locally installed modules and we remove those after `phase II` to be built again properly. now, if we use...
- [ ] list dependency (inc. recursive list by specific flag) for given package/s - [ ] find all dependent packages (inc. recursive list by specific flag) for given package/s
pakket and the repo web-service (or anything specific to server-side) should be separated to different packages (client doesn't need Dancer2 and other dependencies).