Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename to nts #597

Closed
wants to merge 1 commit into from
Closed

Rename to nts #597

wants to merge 1 commit into from

Conversation

cgwalters
Copy link
Member

@cgwalters cgwalters commented Jan 30, 2017

This is in concert with ostreedev/ostree#659. We
can now talk coherently about nts when that's what we mean, rather than
just the base libostree. I've heard many people talk about "ostree layering",
but no such thing exists 😃. Also, nts is just shorter to say, and type, etc.

It's a net-new brand, but I think that's OK.

Obviously, there's a lot more changes we could do here, but I don't want to
create conflicts, just start the ball rolling.

This is in concert with ostreedev/ostree#659.  We
can now talk coherently about `nts` when that's what we mean, rather than
just the base libostree.  I've heard many people talk about "ostree layering",
but no such thing exists 😃.  Also, `nts` is just shorter to say, and type, etc.

It's a net-new brand, but I think that's OK.

Obviously, there's a lot more changes we could do here, but I don't want to
create conflicts, just start the ball rolling.
@cgwalters
Copy link
Member Author

Previously: #405

@jberkus
Copy link

jberkus commented Jan 30, 2017

"nts"? what's that stand for? Why not "rost"? My worry would be that "nts" is close enough to "ntp" that folks might get confused about it.

Regardless, if we're going to rename the utilities (including ostree) then we'll need a transition period with a symlink to the old names.

@cgwalters
Copy link
Member Author

"nexus tree system", see the discussion in #597 (comment)

And yes, rpm-ostree -> nts for the conceivable future (it's all already implemented, including an alias for the systemd unit).

@jberkus
Copy link

jberkus commented Jan 30, 2017

Longer comment on #397, since that's where discussion is.

In short: -1 from me.

@cgwalters
Copy link
Member Author

Wrong comment link? We should probably keep this in #405

@jberkus
Copy link

jberkus commented Jan 30, 2017

@cgwalters sorry, meant #405.

@rh-atomic-bot
Copy link

☔ The latest upstream changes (presumably 12448b9) made this pull request unmergeable. Please resolve the merge conflicts.

@cgwalters cgwalters added the WIP label Mar 10, 2017
@cgwalters
Copy link
Member Author

@cgwalters Thanks for submitting this PR, but it's way outdated now...IMO not worth keeping around on our PR list. If we were to do something here it'd likely end up being quite different anyways.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants