[devel] Мечты об экспансии

[Alexey I. Froloff]

On Sun, May 31, 2009 at 12:11:57AM +0400, Alexey Rusakov wrote:
> Да, забрось, интересно.
00:42 -!- arekm (i=arekm at pld-linux/arekm) has joined #altlinux
00:42 <arekm> hello, I have few question about your cvs->git conversion. Anyone with the knowledge alive?
00:59 <raorn> arekm: best way to convert cvs to git is to use parsecvs
00:59 <raorn> arekm: but you need access to raw cvsroot
01:00 <raorn> this is possible with sf.net or savannah, they allow anon rsync access
01:01 <arekm> raorn: I'm not interested in strict conversion process, more about altlinux layout, commit scripts, automatization and such
01:01 <raorn> arekm: there's special package called gear
01:02 <arekm> where? http://git.altlinux.org/archive/g/gear don't see it here
01:02 <Lost> arekm: there was no cvs->git conversion except for kernel
01:02 <arekm> Lost: didn't altlinux use cvs for specs/sources?
01:02 <raorn> arekm: people/ldv/packages/gear.git
01:02 <Lost> no
01:02 <Lost> only for kernel
01:02 <raorn> no cvs, only git
01:03 <arekm> uh, so what was used?
01:03 <raorn> nothing ;-)
01:03 <arekm> ups 8)
01:03 <Lost> each maintainer had own version
01:03 <raorn> one repo - one package
01:04 <Lost> svn/cvs/darcs etc :)
01:04 <raorn> well, not exactly one
01:04 <Lost> всем спокойной ночи!
01:04 <raorn> there were no official VCS for specs before
01:06 <raorn> all mintainers now have his own repo for each package. we pull changes from other maintainers
01:11 <raorn> gear just prepares all tarballs, patches and spec and then it just passes it to rpmbuild or hasher
01:21 <raorn> arekm: so, you want to migrate to git? ;-)
01:21  * raorn .oO( щас ldv начнут багрепорты из плд слать ;-))) )
01:21 <arekm> raorn: considering it but spliting flat cvs into git tree looks like nightmare
01:23 <raorn> arekm: i don't think it's possible. but you can take one xxx.spec,v and convert it to git, then take next, then next, and finally you will kill yourself ;-)
01:23 <wart> arekm: git-cvsimport?
01:23 <raorn> wart: ONLY parsecvs
01:24 <wart> Or you don't have a strict CVSROOT<->git repo correspondence?
01:24 <wart> raorn: Or parsecvs. They're both crappy, in fact.
01:24 <raorn> cvsimport sucks cock
01:24 <arekm> wart: the problem is not with the cvs->git conversion. The problem is with making flat->tree conversion
01:24 <raorn> arekm: take one file from repo and feed it to parsecvs
01:25 <wart> arekm: Could you elaborate?
01:25 <raorn> arekm: or you can use gear-srpmimport
01:25 <wart> On flat->tree. I didn't quite get it.
01:25 <raorn> if you can export all versions of a package
01:25 <arekm> wart: see http://cvs.pld-linux.org/SPECS/ and http://cvs.pld-linux.org/SOURCES/ - flat for all packages
01:26 <raorn> arekm: in gear terms, package is not just spec, but sources and packages in one git tree
01:26 <arekm> so you don't really (easily) know which file belongs to which package
01:26 <wRAR> so the problem is in separating the sources of different packages into different trees?
01:26 <raorn> *patches
01:26 <arekm> wRAR: yes (on all branches/tags)
01:26 <wart> arekm: Well, you could create a whole bunch of srpms and import them with gear.
01:26 <wart> Of course, you'll loose history then.
01:27 <raorn> this is what i told before
01:27 <arekm> wart: and i want/need history
01:27 <raorn> what "history"?
01:27 <arekm> of specs/sources
01:27 <wart> raorn: CVS history. For specs.
01:27 <raorn> history of package changes or history of spec editions?
01:27 <wart> CVS history.
01:27 <raorn> why?
01:27 <wart> If it's not the same as package log, it's trashed.
01:28 <raorn> who need this?
01:28 <wRAR> needs what?
01:28 <wart> Why do you need git/cvs, then?
01:28 <wRAR> editing history?
01:28 <raorn> cvs history
01:28 <wRAR> editing history?
01:28 <wRAR> or any history?
01:28 <raorn> not "who". why?
01:28 <wart> Because that's what version control is all about.
01:29 <raorn> what is "version"?
01:29 <wRAR> bb all
01:29 <wart> raorn: cvs commit.
01:29 <raorn> cvs commit is just transport
01:29 <wart> raorn: We're talking about version control now.
01:30 <raorn> what "version" you want to control and why?
01:30 <wart> raorn: Кончай тупить.
01:30 <raorn> ты тупишь
01:30 <wart> Это ты тупишь.
01:30 <wart> У человека cvs history.
01:30 <wart> спеков
01:30 <wart> И он не хочет её потерять.
01:30 <wRAR> raorn: где ты предлагаешь историю спека взять ещё?
01:31 <wRAR> или предлагаешь забить?
01:31 <wart> arekm: I think that it won't be hard to modify gear to support your scheme.
01:32 <wart> arekm: As an import source.
01:32 <arekm> btw. /me wonders if there are realtime translations for irssi (using google translate for example)
01:32 <arekm> wart: will check
01:32 <arekm> s/translations/translators/
01:32 <raorn> does it matter, were there 10 changes in spec or just 1 change between two subsequent versions of a package?
01:32 <wart> Hell yes it does.
01:32 <arekm> it does
01:33 <raorn> oh
01:33 <wRAR> блин
01:33 <raorn> why?
01:33 <wRAR> raorn: а где ты ещё возьмёшь "change between two subsequent versions of a package"?
01:33 <arekm> so you know who broke things in middle for example
01:33 <raorn> wRAR: по тегу, если они есть
01:33 <wart> Тэгу где?
01:33 <wRAR> а
01:33 <wRAR> тегу в цвсе
01:33 <raorn> в cvs, блин
01:33 <wRAR> а разница?
01:34 <raorn> релиз пакета тежится
01:34 <wart> Ты же предлагаешь выкинуть cvs.
01:34 <wart> Вместе с тэгами.
01:34 <wart> Да и индивидуальные изменения знать надо.
01:34 <raorn> именно. это называется "миграция с частичным сохранением истории"
01:35 <wart> Он и спрашивает -- как её сохранить. А наделав srpm'ов не будет ничего.
01:35 <raorn> arekm: what do you wand to do? completly migrate from cvs to git? or something else?
01:37 <arekm> raorn: completly migrate. I was thinking that altlinux used cvs before but well, I was wrong
01:37 <wart> ALTLinux doesn't use git even know.
01:38 <wart> now
01:38 <raorn> we don't build packages directly from git on build server
01:38 <arekm> ehm, so what's the purpose of git.altlinux.org?
01:39 <wart> git hosting
01:39 <raorn> arekm: well, in this case you can sacrifice detailed history. those packages already released. simpliest way is to import all srpms with gear-srpmimport
01:39 <arekm> and what about /archives/ on it?
01:39 <raorn> old package history
01:40 <raorn> all packages imported in git from srpms
01:40 <arekm> so it's just for hosting history of released packages, am I correct?
01:40 <wart> arekm: There will be The Day, when packages will be built from git. But nobody knows when.
01:40 <wart> Unreleased also.
01:40 <raorn> ldv is working on that
01:40 <wart> Something like alioth for Debian, if you know.
01:41 <wart> git hosting so that people could collaborate
01:42 <raorn> arekm: for me, it's easier to track upstream VCS in separate branch and keep all changes as commits, not patch files
01:42 <raorn> in this case i don't use package/spec history
01:48 <raorn> arekm: in alt linux you don't have to use git if you want to build packages. and /archive/ is just holding history for those who want to keep it when they start using git

По последним данным они так ещё и не определились с переездом, но
от своей плоской структуры уже собираются уходить.

-- 
Regards,
Sir Raorn.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.altlinux.org/pipermail/devel/attachments/20090531/67c01adc/attachment.bin>