svn 和 nano 问题

发布于 2024-10-10 11:48:18 字数 1011 浏览 5 评论 0原文

我正在尝试将 svn 配置为在我的计算机(Ubuntu)上本地运行,但遇到了一些问题。按照官方 svn-redbooks 教程中的逐字说明进行操作让我很头疼。

这只是一个简单的 VCS 设置,其中 svn 和 svnadmin 本地安装在 /user/lib 处,而我想要的工作副本(尽管我没有指定/导入它作为工作副本)位于 /home/myUser/我的项目。我的 svn 存储库将位于 /opt/sandbox/svn

我希望我的存储库能够能够存储多个项目,每个项目都实现标准的“主干、分支、标签”目录。

另外,我不需要任何安全/身份验证配置,因为这只是我本地计算机上我自己的项目的版本控制。

所以我猜设置的逻辑流程是:
(1) 在/opt/sandbox/svn创建存储库
(2) 将myProj项目目录添加到存储库
(3) 在myProj内添加trunk/、branches/和tags/目录
(4)指定/home/myUser/myProj为/opt/sandbox/svn/myProj/trunk的工作副本
(5) 将 /home/myUser/myProj 添加到 /trunk

顺便说一下,不要担心为主干与分支等设置此设置的逻辑。我只是在找人演示如何在 svn 中为项目设置源代码控制,稍后我会担心我的内部“版本控制过程”(从任何目录推/拉等)!

不知道该怎么做。 另外,每当我使用 file:/// 运行任何命令时(我必须这样做,因为它是本地 svn),而不是执行终端的命令只是打开一个实例nano 就像它想让我编辑一些东西。

那么有人可以阐明一下:
(1)我上面指定的逻辑流程是否正确,如果不正确,需要修改什么;和
(2)我需要运行哪些终端/svn命令来实现正确的逻辑流程;和
(3) 纳米业务进展如何?

谢谢!!!

I'm trying to configure svn to run locally on my machine (Ubuntu) and am having some problems. Following the instructions - verbatim - from the official svn-redbooks tutorial is causing me headaches.

This is just a plain-jane VCS setup, with svn and svnadmin installed locally at /user/lib and my intended working copy (though I have not specified/imported it as a working copy) located at /home/myUser/myProj. My svn repository will be located at /opt/sandbox/svn

I want my repository to be capable of storing multiple projects, each of them implementing the standard "trunk, branches, tags" directories.

Also, I don't need any security/auth config since this is just version control for my own projects on my local machine.

So I'm guessing the logical flow of setting this up would be:
(1) Create the repository at /opt/sandbox/svn
(2) Add the myProj project directory into the repository
(3) Add trunk/, branches/ and tags/ directories inside of myProj
(4) Specify /home/myUser/myProj to be the working copy of /opt/sandbox/svn/myProj/trunk
(5) Add /home/myUser/myProj into the /trunk

On a side note, don't worry about the logic of setting this up for the trunk vs. branches, etc. I'm just looking for someone to demo how source control is set up for a project in svn, and I'll worry about my internal "version control process" (pushing/pulling from whichever directory, etc.) later on!

For the life of me I can't figure out how to do this. Plus, whenever I run any commands using file:/// (I have to since it's a local svn), instead of the command executing the terminal just opens up an instance of nano like it wants me to edit something.

So can someone shed some light as to:
(1) Whether or not the logical flow I specified above is correct, and if not what needs to change; and
(2) What terminal/svn commands I need to run to implement the correct logical flow; and
(3) What is going on with that nano business?

Thanks!!!

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

黑白记忆 2024-10-17 11:48:18

首先,我不会将存储库称为沙箱。该术语通常与工作副本同义。也许 /opt/repository/svn 打字越少对我来说越好,所以我会这样做 /opt/repo

为了避免启动编辑器,请使用:

svn commit -m "my commit message" somefiles.*

或以速记形式提交所有内容

cd working_copy
svn ci -m ""

1)逻辑流程很好

2)初始布局命令

svn co file:///opt/repository/svn
cd svn
mkdir -p trunk/myProj branches/myProj tags/myProj
svn add *
svn ci -m "initial layout"

擦除顶层签出

rm -rf trunk branches tags

创建您的项目

svn co file:///opt/repository/svn/trunk/myProj
cd myProj
svn add *
svn ci -m "initial project layout"

3) nano fix = commit -m

First off, I wouldn't call the repository sandbox. This term is usually synonymous with working copy. Maybe /opt/repository/svn The less typing the better for me so I'd do /opt/repo

To avoid launching the editor use:

svn commit -m "my commit message" somefiles.*

or to commit everything in shorthand

cd working_copy
svn ci -m ""

1) logical flow is good

2) inital layout commands

svn co file:///opt/repository/svn
cd svn
mkdir -p trunk/myProj branches/myProj tags/myProj
svn add *
svn ci -m "initial layout"

wipeout top level checkout

rm -rf trunk branches tags

create your project

svn co file:///opt/repository/svn/trunk/myProj
cd myProj
svn add *
svn ci -m "initial project layout"

3) nano fix = commit -m

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文