| delorie.com/archives/browse.cgi | search |
> > who is going to advice the package maintainers to check for these file > > conflicts?! > > Well if we can lint the packages at upload time, I guess Chris will get > the failure message (Chris, I'm happy to be copied on that if you want). > Otherwise, I think you(Stipe)'ll have to do it for now. I would like to do so. Is there any reference who (i.e. which person) is responsible for which package?! Maybe an database would help here to keep track of maintainers for certain packages and even more for "bug reporting" concerning the single packages. The maintainer would have the chance to see if users have notices problems with her/his package and react to realease a new cycle. > Do you mean that if one package is dependent on another, you will > announce the conflict, and if they are not you won't? The file conflict is currently always announced. Semanticaly a file conflict between related (dependable) packages is less worse than a file conflict between unrelated packages. We assume that a usage of a specific file between two unrelated packages has more potential for problems. I guess this is obvious. > Yes, sort of, see "package naming". I don't see that we need to enforce > one or other compression format right now. this is true -- I'm only peaking on packages that become really big, like the xfree86 packages or others. bzip2 is noticable better here. Stipe tolj AT wapme-systems DOT de ------------------------------------------------------------------- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: info AT wapme-systems DOT de Internet: http://www.wapme-systems.de ------------------------------------------------------------------- wapme.net - wherever you are
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |