<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Le 07/02/2017 à 14:06, Awal Garg via aur-requests a écrit :<br>
</p>
<blockquote
cite="mid:CABsO8a7AkqV=VBN2ecMix_WUY4qPQ1rLM=9O0nB=NXV6wYZKkQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div dir="ltr" class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">> You apparently didn’t even
asked the maintainer of firefox-developer<br
class="gmail_msg">
about that move.<br class="gmail_msg">
<br class="gmail_msg">
</div>
</div>
</div>
</div>
</div>
<div dir="ltr" class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">Apologies, I didn't realize I
should be doing that first.<br class="gmail_msg">
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Contacting the maintainer before filing a request is a good
practice, whether you ask his package to be orphaned, deleted or
merged into another. ;) <br>
<br>
Maybe we should patch
<a class="moz-txt-link-freetext" href="https://git.archlinux.org/aurweb.git/tree/web/template/pkgreq_form.php?h=v4.4.1">https://git.archlinux.org/aurweb.git/tree/web/template/pkgreq_form.php?h=v4.4.1</a>
to add that for merge and deletion (it’s already there for orphan).<br>
<br>
<blockquote
cite="mid:CABsO8a7AkqV=VBN2ecMix_WUY4qPQ1rLM=9O0nB=NXV6wYZKkQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div dir="ltr" class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">> Also, firefox-developer is the
correct name, if<br class="gmail_msg">
> anything it’s firefox-dev that should be merged in
firefox-developer.<br class="gmail_msg">
<br class="gmail_msg">
</div>
</div>
</div>
</div>
<div dir="ltr" class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">That is indeed what I mentioned in
the original request, but I figured it<br
class="gmail_msg">
</div>
<div class="gmail_msg">made more sense to have the outdated
package get merged in the<br class="gmail_msg">
</div>
<div class="gmail_msg">updated one and rename the new one
instead.<br class="gmail_msg">
</div>
</div>
</div>
</div>
</blockquote>
<br>
Since renaming = pushing a package with the new name + filing a
request to merge the old one in the new one, this doesn’t make any
sense.<br>
<br>
<blockquote
cite="mid:CABsO8a7AkqV=VBN2ecMix_WUY4qPQ1rLM=9O0nB=NXV6wYZKkQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div dir="ltr" class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">> That being said, both packages
need some fixing, and auto-updating a<br class="gmail_msg">
> VCS-like package is not a good practice<br
class="gmail_msg">
<br class="gmail_msg">
</div>
</div>
</div>
<div dir="ltr" class="gmail_msg">Agreed.<br>
<br>
</div>
<div class="gmail_msg">I'll take a better look at your nightly
PKGBUILD and see if I can<br>
</div>
<div class="gmail_msg">co-maintain firefox-developer. Thanks.<br>
</div>
</div>
</blockquote>
<br>
That’s OK. I’ll monitor the situation with
firefox-aurora/firefox-dev/firefox-developer from now on, and will
wait for things to be settled before accepting the current remaining
requests.<br>
<br>
Regards,<br>
Bruno<br>
</body>
</html>