<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>If the package needs to be deleted, go on. Do it.<br>
If we have to fill up a mailing list just for this, it would be
better to just delete the package. <br>
</p>
<p>The package was reuploaded automatically, because I dindn't turn
off the auto-maintainer once the first package deletion happened.<br>
I then stopped once the package was deleted for the second time.</p>
<p>I proceeded to add the package again when I noticed that <a
href="https://aur.archlinux.org/account/jnbek" title="View
account information for jnbek">jnbek</a> was one version behind,
despite the numerous complains about the package not being
updated.</p>
<p>Look, if you guys don't want an automatically updated package,
it's okay. I'm not getting paid from nobody to keep it up and
running.<br>
My only goal was to provide a reliable AUR package for the Firefox
Developer Edition - I never intended to break any rule, nor to
turn the whole AUR community against me.</p>
<p>It is up to you, the sources for the auto-maintainer are <a
href="https://github.com/denysvitali/aur-firefox-dev-automaintainer">here</a>,
the package itself is reliable. <br>
</p>
<p>Sure, in the an "hands on check to ensure everything went well"
before publishing it is not performed (because yeah, it is
automaintained), but in 36 releases I never really needed to do
anything, and there was no problem at all.</p>
<p>I guess the choice now is the following:</p>
<p>1) Keep firefox-dev and merge it into firefox-developer<br>
2) Delete firefox-dev, keep firefox-developer and hope the new
maintainer provides a release as soon as it comes out<br>
3) Delete firefox-developer and change the way the releases are
rolled out<br>
4) Keep everything as is, and let the user choose if they want
rolling out releases, or a more "stable" approach<br>
5) ???<br>
</p>
<p>Please note that `firefox-dev-ru` follows my same principle, and
also note that <a moz-do-not-send="true"
href="https://aur.archlinux.org/packages/?O=0&K=firefox-dev">by
searching for firefox-dev*</a> half of the results are packages
that aren't updated.</p>
<p>Keep also in mind that now the firefox-developer package has got
a new maintainer, but has been updated to the newest
57.0a1.20170830-1 version, which isn't officially rolled out yet.</p>
<br>
<p>I hope this message explains my reasons behind the choices of the
firefox-dev package - I was (and still am) just trying to improve
the Firefox Developer AUR experience.<br>
</p>
<br>
<div class="moz-cite-prefix">On 30. 08. 17 19:31, John D Jones III
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:6d58de82-9c20-fd07-ccd5-ea325eb941bd@gmail.com">On
8/28/17 13:54, <a class="moz-txt-link-abbreviated" href="mailto:notify@aur.archlinux.org">notify@aur.archlinux.org</a> wrote:
<br>
<blockquote type="cite">jnbek [1] filed a deletion request for
firefox-dev [2]:
<br>
<br>
This package has been a hostile attempt at taking control of the
<br>
formerly my firefox-developer PKGBUILD, which is built by strict
<br>
standards for Mozilla software. This PKGBUILD autoupdates willy
nilly
<br>
without any hands on checks to ensure everything went well.
<br>
<br>
[1] <a class="moz-txt-link-freetext" href="https://aur.archlinux.org/account/jnbek/">https://aur.archlinux.org/account/jnbek/</a>
<br>
[2] <a class="moz-txt-link-freetext" href="https://aur.archlinux.org/pkgbase/firefox-dev/">https://aur.archlinux.org/pkgbase/firefox-dev/</a>
<br>
<br>
</blockquote>
It's also worth noting that the firefox-dev PKGBUILD was already
deleted from the AUR and denvit readded it anyways.
<br>
<br>
</blockquote>
</body>
</html>