Date: Mon, 10 Sep 2012 12:55:51 -0700 (PDT) From: Jeffrey Bouquet <jeffreybouquet@yahoo.com> To: Kevin Oberman <kob6558@gmail.com> Cc: Jamie Paul Griffin <jamie@osx.kode5.net>, freebsd-ports@freebsd.org Subject: Re: [HEADS-UP] Announcing the end of port CVS Message-ID: <1347306951.98429.YahooMailClassic@web111314.mail.gq1.yahoo.com> In-Reply-To: <CAN6yY1tTdhpDx9QARmaiQ58buB0mJADDqWdF7QCenL6OHQEAFQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
=0A=0A--- On Sat, 9/8/12, Kevin Oberman <kob6558@gmail.com> wrote:=0A=0A> F= rom: Kevin Oberman <kob6558@gmail.com>=0A> Subject: Re: [HEADS-UP] Announci= ng the end of port CVS=0A> To: "Jeffrey Bouquet" <jeffreybouquet@yahoo.com>= =0A> Cc: "Jamie Paul Griffin" <jamie@osx.kode5.net>, freebsd-ports@freebsd.= org=0A> Date: Saturday, September 8, 2012, 10:15 PM=0A> On Sat, Sep 8, 2012= at 4:08 PM,=0A> Jeffrey Bouquet=0A> <jeffreybouquet@yahoo.com>=0A> wrote:= =0A> >=0A> >=0A> > --- On Sat, 9/8/12, Kevin Oberman <kob6558@gmail.com>=0A= > wrote:=0A> >=0A> >> From: Kevin Oberman <kob6558@gmail.com>=0A> >> Subjec= t: Re: [HEADS-UP] Announcing the end of port=0A> CVS=0A> >> To: "Jamie Paul= Griffin" <jamie@osx.kode5.net>=0A> >> Cc: freebsd-ports@freebsd.org=0A> >>= Date: Saturday, September 8, 2012, 2:42 PM=0A> >> On Sat, Sep 8, 2012 at 3= :09 AM, Jamie=0A> >> Paul Griffin <jamie@osx.kode5.net>=0A> >> wrote:=0A> >= > > [ Lars Eighner wrote on Fri=A0 7.Sep'12 at=0A> 10:00:45=0A> >> -0500 ]= =0A> >> >=0A> >> >> On Fri, 7 Sep 2012, Beat Gaetzi wrote:=0A> >> >>=0A> >>= >> >The development of FreeBSD ports is=0A> done in=0A> >> Subversion nowa= days.=0A> >> >> >For the sake of compatibility a=0A> Subversion to=0A> >> C= VS exporter is=0A> >> >> >in place which has some limitations.=0A> For CVSu= p=0A> >> mirroring cvsup=0A> >> >> >based on Ezm3 is used which breaks=0A> = regularly=0A> >> especially on amd64=0A> >> >> >and with Clang and becomes = more and=0A> more=0A> >> unmaintainable.=0A> >> >>=0A> >> >>=0A> >> >> What= exactly is the motivation again for=0A> moving=0A> >> from things which wo= rk like=0A> >> >> cvsup and gcc to things that are broken or=0A> lame=0A> >= > like subversion and clang?=0A> >> >=0A> >> > They're not broken. I've rec= ently been using=0A> them and=0A> >> they're fine.=0A> >> > There has been = plenty of discussion about the=0A> reasons=0A> >> for the changes so=0A> >>= > have a read from the various sites and list=0A> archives.=0A> >>=0A> >> = Looks like a troll to me. No one who has worked=0A> with=0A> >> subversion = for a=0A> >> project of any size would ever want to go back to=0A> CVS. Whi= le=0A> >> still=0A> >> having some of CVS's limitations, it does far, far= =0A> more and=0A> >> is much=0A> >> easier to work with for most things. I = really miss=0A> the=0A> >> forced commit=0A> >> and, for one application, R= ANCiD, I use CVS so I=0A> can grep=0A> >> through the=0A> >> ,v files easil= y. But I can't see any reason for=0A> FreeBSD not=0A> >> to move=0A> >> the= the more advanced system.=0A> >>=0A> >> As to clang, there is no choice th= ere. The license=0A> on newer=0A> >> version of=0A> >> gcc (GPLv3) is simpl= y not acceptable to the=0A> community, so=0A> >> gcc is stuck=0A> >> foreve= r at 4.2 which is getting very old. clang=0A> has=0A> >> excellent=0A> >> d= evelopment support, an acceptable license, and=0A> early tests=0A> >> show = that=0A> >> it generally compiles faster and MAY even generate=0A> better,= =0A> >> faster=0A> >> code.=0A> >> --=0A> >> R. Kevin Oberman, Network Engi= neer=0A> >> E-mail: kob6558@gmail.com=0A> >> ______________________________= _________________=0A> >> freebsd-ports@freebsd.org=0A> >> mailing list=0A> = >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports=0A>; >> To unsubs= cribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"=0A> >>=0A> = >=0A> > I'd not go so far as to label it trolling....=0A> =0A> The language= was highly pejorative, so it felt troll like.=0A> > ...=0A> >=A0=A0=A0I se= arched quite a bit upon this=0A> announcement to find csup > svn equivalent= guides and=0A> found little applying to ports...=0A> > hopefully they will= appear prior to the changeover?,=0A> something=0A> > easily learned?=0A> = =0A> Good point. I found the handbook information adequate, but=0A> not as = easy=0A> to follow as it might be.=0A> Guess I'll write one. It's really qu= ite easy and much faster=0A> then csup.=0A> =0A> 1. Install devel/subversio= n=0A> 2. Select US east coast or US west as your server. Pick at=0A> random= or=0A> pick the one closer to you.=0A> 3. Rename (mv) ports/distfiles and = ports/packages out of=0A> /usr/ports=0A> 4. rm -r /usr/ports/*=0A> 5. svn c= o http://svn0.us-west.freebsd.org/ports/head /usr/ports=0A> =A0=A0=A0OR=0A>= =A0=A0=A0svn co http://svn0.us-east.freebsd.org/ports/head /usr/ports=0A> = =A0=A0=A0Ports will now be checked out of the=0A> repository and written to= /usr/ports=0A> 6. make -f /usr/ports/Makefile fetchindex=0A> 7. Move ports= /distfiles and ports/packages back into=0A> /usr/ports. Since=0A> these dir= ectories are not in the repository, they will be=0A> ignored by=0A> updates= .=0A> 7. Update ports as needed with 'svn up /usr/ports' and 'make=0A> -f= =0A> /usr/ports/Makefile fetchindex'=0A> =A0=A0=A0This step does the equiva= lent of csup.=0A> 8. Use the Subversion manual from http://svnbook.red-bean= .com/ to=0A> learn how to other things with svn. Of particular interest=0A>= is 'svn=0A> info /usr/ports and setting up the .subversion file to do=0A> = things like=0A> ignore some directories.=0A> If you add private ports to /u= sr/ports, they will be ignored=0A> by svn as=0A> they don't exist in the re= pository.=0A> =0A> If anyone has suggestions on other things that belong in= =0A> this list,=0A> please let me know.=0A> >=0A> > ....=0A> > (disregardin= g portsnap for the moment, and I=0A> apologize...)=0A> > ....=0A> > (the .h= tm I saved from the web searches (svn) appear=0A> too complex and=0A> > irr= elevant to this use case to be of use here...)=0A> > ...=0A> > As a minor a= side, /devel/apr1/ is a dependency of=0A> subversion at=0A> > least on this= machine probably...=0A> > ...=0A> =0A> Yes, svn can pull in several depend= encies.=A0 I'll admit=0A> that I don't=0A> know why apr1 is needed.=0A> =0A= > > All the many FreeBSD texts I've read and used, maybe=0A> one of them=0A= > > has a relevant chapter? And/or maybe complete SVN=0A> instructions=0A> = > should be added to the UPDATING file as well as a=0A> section on=0A> > po= rts in the subversion manpage(s).=0A> =0A> Have you read the FreeBSD handbo= ok? It does not have the=0A> step-by-step=0A> instructions I listed, but I = figured out how to use svn=0A> after reading=0A> that information and about= 30 minutes of experimentation.=0A> Also, these=0A> same instructions can b= e use (with trivial modification) to=0A> update=0A> FreeBSD sources.=0A> = =0A> > All taken as constructive discussion hopefully.=A0 I=0A> re-edited t= his=0A> > email to make it shorter and less critical...=0A> =0A> Yes, this = mail expressed reasonable concerns without=0A> sounding=0A> confrontational= . Hopefully my answers help.=0A> -- =0A> R. Kevin Oberman, Network Engineer= =0A> E-mail: kob6558@gmail.com=0A> ________________________________________= _______=0A> freebsd-ports@freebsd.org=0A> mailing list=0A> http://lists.fre= ebsd.org/mailman/listinfo/freebsd-ports=0A> To unsubscribe, send any mail t= o "freebsd-ports-unsubscribe@freebsd.org"=0A> =0A=0AI followed this procedu= re with the exception of "svn co" atop=0Athe exiting ports tree (less distf= iles, etc moved back later...)=0Avs removing the ports tree first. Now no = command I find accomplishes=0Athe same as a simple csup of, say, graphics w= ithout either no=0Aerror message or a terse one...=0A...=0Asvn commit /usr/= ports=0Asvn: E155015: Aborting commit: '/usr/ports/accessibility' remains i= n conflict=0A...=0Asvn resolved /usr/ports/accessibility=0Aappears to not p= ermanently fix the problem.=0A...=0AAs csup-after-svn is supposedly not any= longer to be used on=0Athe ports tree (correct?) I searched the freebsd fo= rums 'checkout'=0Aand practically none of the threads referred to the ports= tree.=0ANor the online documentation (wikis, manuals) as they require=0Aex= tensive study which I'd rather not spend hours on.=0A...=0AI should remove = .svn and use csup until documentation appears, or=0Asetup a .svn server whi= ch is "original" and might not give errors,=0Afrom which to ftp/rsync_via_t= humbdrive, or someone knows ports-specific svn commands which 'just work' a= s csup would? i.e.=0Amore or less a binary failure: it works or it doesn't.= .. =0A=0AThanks for any advice. Unable to update ports on one machine=0Aun= til I decide how to proceed...=0A=0AJ. Bouquet
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1347306951.98429.YahooMailClassic>