Re: libmrproject
Mikael Andersson <[email protected]> 09 May 2003 18:42:36 +0200
| Newsgroups | gmane.comp.gnome.apps.mr-project.user |
|---|---|
| Organization | Debian |
| Message-ID | <1052498556.9437.33.camel@ibmmia> |
fre 2003-05-09 klockan 18.07 skrev C.J. Collier: > On Fri, 2003-05-09 at 00:19, Mikael Andersson wrote: > > tor 2003-05-08 klockan 20.02 skrev C.J. Collier: > > > Is there a reason the libmrproject/debian/ directory is not in the > > > libmrproject CVS repository? > > > > > > > You mean in the upstream cvs repository? It's exists some issues with > > that, and I have it in my own CVS repo. Sometimes I also add patches > > wish is not in the released version, and that is more complicated to do > > if you have it in the upstreams CVS repo. Why do you want to have it in > > upstreams CVS repo? > > Because I've got read access to the upstream CVS repository (but not > yours), and they might let you have write access if they knew it would > benefit the project. Duplication of data == bad. ;) If the debian/ > directory is in the CVS repository, then all I have to do is cvs update; > debian/rules; to build the most recent CVS .deb myself. I like having > my programs installed from .deb AND CVS. Yes, I think that it's possible for me to get write access to the cvs repro, but I'm not sure if it would make things easier. Today we doesn't have any duplication of the debian directory, so I doesn't think that it's an argument, but maybe that it's distributed over different places. The cvs-buildpackage way of creating deb package is slow if it doesn't work against a fast cvs server. Today I'm working against a local cvs server, and I tried to access a cvs server over a 512kbit link, but it was to slow. I now have a 2MBit link, so it's maybe time to check out if it's fast enought. Even if I have the debian directory in the upstream cvs repo, it need some magic to work correctly with some random cvs checkout, and will probaply not always work. I doesn't follow the mrproject development enought to make it work well at time between releases. What I have done before is to release some debs for pre versions on my private apt-repository. I haven't done that for the 0.10pre version, yet, but if it will help people I can do it. What you can do to is to copy the debian directory from the mrproject 0.9.1 source deb to a debian directory in your checked out version of mrproject and modify it to work with the cvs version. Sincerely Mikael