Le Mon, May 25, 2009 at 06:09:58PM +0200, David Paleino a écrit : > On Mon, 25 May 2009 23:01:08 +0900, Charles Plessy wrote: > > > I am sure that there would be a lot of experience and kudos to gain by > > helping > > us to establish a ‘blends+mr’ workflow. Actually, current progresses are > > slow > > enough that you could take easily the leadership :) > > Where can I read more about this?
Hi David, sorry for ignoring you for a week. I have a stupid ‘last-in-first-out’ for my mailbox, and got a sudden burst new emails :) [Actually, if somebody knows a way to move emails up and down in the otherwise date-sorted and threaded mailbox display of Mutt, it would help me to use smarter reply strategies.] I have summarised my thoughts about Blends and ‘mr’ in the following email: ‘http://lists.debian.org/debian-med/2009/05/msg00035.html’. Here are extra comments. With the availability of ‘debcheckout’, it is possible to check out our packages individually in a very easy way. To get them all in one command, it is possible to do a ‘svn checkout’ on the whole package directory of our Subversion repository. There are nevertheless corner cases: - First, some packages very popular among our users are not maintained in our repository but in other's, in particular Debichem's, Debian Science's and the Perl team's. - Second, if we start to use Git, we can not have one command to check out all the packages, as the paradigm there is to have one package per commit. I investigated the possibility to maintain a ‘mr’ configuration file in our Subversion repository, that people would check out and use to then check out all the packages we distribute in our Blend metapackages. This comes with the drawback that the repository containing the mr configuration file and the checked out repositories are difficult to move after. This is why I am now thinking that a more suitable alternative would be to have a tool that can (re-)generate a mr configuration file using the Ultimate Debian Database and a Blends task file (these files contain or should contain the VCS information of prospective packages). In addition, it would save the time of having to maintain a reference configuration file by hand :) http://wiki.debian.org/UltimateDebianDatabase Such a tool would not only be useful to Debian Med, but to the Blends communauty in general, and is a good excuse to learn the UDD. Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
