[Savannah-dev] Re: epm and savannah patch manager

[Mathieu Roy]

address@hidden (Karl Berry) a tapoté :

>     (moved to savannah-dev)
>
> Just for future reference, what is the difference between
> savannah-hackers and savannah-dev?  From the names, I would have guessed
> they were the same.

savannah-hackers is related to the administration of the Savannah
installation at subversions.gnu.org.
savannah-dev is related to the development of the program called
Savannah.

>     The current patch tracker, builtin, in the production version no
>     longer exists in the development version of Savannah.
>
> So with the next release there will be no patch manager at all?

There will be one, but which has nothing in common with the current
one. The new one is an extension of the current bug tracker.

>     In the case of epm, it does not seems to be a project management
>tool of patch but a personal patch management.
>
> That is true, but the reason rms thought of it is that there is a lot of
> overlap in functionality.  The kinds of things that an individual wants
> to manage many patches is the same as what a "project" wants, namely
> define dependencies, add new patches, modify patches, and so on.

Dependencies exists in the patch tracker in the development
branch. However, it depends of the kind of dependancies we are talking
about.
It can defines dependancies on other items on Savannah, not
specifically on a library: but in this last case, this would be purely
informative in the context of a project patch tracker.

By modifying patches, I'm not sure I clearly understand: a priori, a
patch purpose is to be included in a project CVS. It is meaningful to
update patches only when you are not in the upstream project and when
upstream people refuses to apply your patches.

Adding new patch, well, hopefully it is already possible to do that :)


>     It does not come to with a web interface
>
> Right, a web interface would have to be built, as I mentioned
> originally.  I was asking about "in theory".  epm is certainly
> insufficient as it stands, but it still seems to me like a reasonable
> basis for building a patch manager.  Not that I'm asking you to do it,
> you understand :).

I'm still doubtful about the possibility of using this tool in a
project. I'm not sure that epm is insufficient for his stated goal but
I'm not sure of its purpose in the group context.

The best would probably to ask the author what he think about that.



-- 
Mathieu Roy

  +---------------------------------------------------------------------+
  | General Homepage:           http://yeupou.coleumes.org/             |
  | Computing Homepage:         http://alberich.coleumes.org/           |
  | Not a native english speaker:                                       |
  |     http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english  |
  +---------------------------------------------------------------------+