![]() ![]() Git init -bare then adding/setting the remote connection, and lastly having you push/pull to transfer the contents. In general, all the references I found on setting up your own git server it has you first perform In general, I followed some tutorials I found on the web and it worked in a fashion (I will explain the side effects that I didn't find out till later). I strongly suspect I'm not setting up the 'Remote' repo right if git is not pulling in the updates that are clearly there.įrom what I recall when I setup my own self-hosted git server, it does matter how you setup the remote host.I'm just using my $HOME dir for practice - I want to iron out the details before letting Poudriere mess around in /usr/ports.My solution to that is to set up my own manually-maintained repo at $url. I only want to pull in a subset of that - a subset that I specify in a list. command # poudriere ports -u -m git+https -M /usr/ports -U $url -p freebsd_kde will pull in EVERYTHING from the $url I feed it.What I'm trying to achieve here is based on the following considerations: But to my surprise, the URL worked - until I started verifying what was actually pulled in, and that led to my creation of this thread. Even with Apache (and finally figuring out how to tell git to accept my self-signed cert without complaining), git was saying that it can't find a repo at URL ! I tried, but got same error.I have Apache set up anyway, it works like I want it to, might as well make use of that. I tried to do my homework to fix that, but got lost, and decided to go with an HTTPS URL instead. file:///usr/local/poudriere/ports/freebsd_kde gave me the error: GIT_DISCOVERY_ACROSS_FILESYSTEM not set.Click to expand.Well, I tried several ways to pull in the repo via the git command:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |