feat: support marking pkg as Draft

[harry-hov]

Description

See (#763 (comment))

@harry-hov Thanks for the clarification, indeed I missed that part where the gnoland binary pushes all that list of packages. I understand well the usage now. A better name than deprecated would be good (like experimental ?), but since it's already supported by golang.org/x/mod let's go with that 🙏 .

@tbruyelle we can still change the name to something better. What about something self-explaining like draft (hugo), unpublishable, restricted or private (NPM).

---

Suggested candidates:

• WIP (work-in-progress)
• Experimental
• Draft (hugo)
• Unpublishable
• Restricted
• Private (NPM)

PS: Open for better names.

cc: @tbruyelle @moul

[moul]

I believe that "private" is the most appropriate option because it indicates a desire to not share the content publicly, regardless of whether it's in progress or finished.

My second preferred choice would be "draft," as it conveys a similar meaning commonly used in publication systems such as blogs.

Btw, what about replacing deprecated with the choice instead of keeping both?

[harry-hov]

I would prefer draft or experimental. Can we have some kind of voting for that?

[harry-hov]

Btw, what about replacing deprecated with the choice instead of keeping both?

Um. I'm not sure what's right. Since we already have deprecated field in *modfile.Module, there is no harm in parsing it. Makes it more compatible with go.mod.

Or we can use custom GnoModule instead of *modfile.Module (I won't recommend this)

// Parsed gno.mod file.
type File struct {
-	Module  *modfile.Module
+       Module  GnoModule
	Go      *modfile.Go
	Require []*modfile.Require
	Replace []*modfile.Replace

	Syntax *modfile.FileSyntax
}

+type GnoModule struct {
+	Mod        module.Version
+	Draft      bool
+	Syntax     *Line
+}

---

PS: I'm fine with both. replacing/keeping deprecated.

[harry-hov]

For now replaced WIP -> Draft

[moul]

Um. I'm not sure what's right. Since we already have deprecated field in *modfile.Module, there is no harm in parsing it. Makes it more compatible with go.mod.

I wasn't aware of this. Let's keep both then.