Giter Site home page Giter Site logo

Comments (9)

Gankra avatar Gankra commented on May 18, 2024

cc @sarahghp

from cargo-dist.

sarahghp avatar sarahghp commented on May 18, 2024

(Assigned myself so I can find it again as I go.)

from cargo-dist.

sarahghp avatar sarahghp commented on May 18, 2024

complete manifest of package contents..?

@Gankra I'm not sure what this means. What are package contents in this case?

from cargo-dist.

sarahghp avatar sarahghp commented on May 18, 2024

README text

We should definitely let people give us accompanying text. I think there's a decent argument that it should be different from the README so that installation text can be focused more than a README might. Would calling it INSTALLATION.md so that people can put it in the repo be good? I say: probably!

Interested in your thoughts on this, too, @ashleygwilliams.

from cargo-dist.

Gankra avatar Gankra commented on May 18, 2024

@sarahghp for "package contents" i was picturing a literal "here is the directory structure and every file in the zip" with additional annotations like "this is an executable, this is...".

from cargo-dist.

sarahghp avatar sarahghp commented on May 18, 2024

@Gankra:

@sarahghp for "package contents" i was picturing a literal "here is the directory structure and every file in the zip" with additional annotations like "this is an executable, this is...".

And do you see that as being generated by us when we ingest? What would it be used for? (I am not against it; I just want to understand.)

from cargo-dist.

Gankra avatar Gankra commented on May 18, 2024

Sorry thought I replied to this. I would expect cargo-dist to produce it, but I don't really have a good usecase.

I can vaguely imagine it being useful as a sort of "users are going to be opinionated and want to tweak locations/names of things, but if we have a listing of where certain semantic files are located then downstream tools don't need to worry about that -- they can just check the manifest for where the license files are, where the release notes are, where the main executable is, etc.

from cargo-dist.

sarahghp avatar sarahghp commented on May 18, 2024

Ah, cool! That makes a lot of sense. Thanks for walking me though it.

from cargo-dist.

Gankra avatar Gankra commented on May 18, 2024

I'm going to call this minimally done, we can file followups for additional fields we want to include. Otherwise this bug will become an endless zombie. (in particular there's no author/repo or build info atm)

from cargo-dist.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.