SeaMonkey/StatusMeetings/2017-05-21: Difference between revisions

SeaMonkey/StatusMeetings/2017-05-21 (view source)

1,340 bytes added , 21 May 2017

Confirmed users

2,078

edits

@@ Line 268: / Line 268: @@
 ==== Callek ====
 ==== ewong ====
+* Updates (i.e. updating SeaMonkey via the update function) is not going to work with anything 2.48b1+.
+Why?
+Because aus2 doesn't (atm) support the newer updates paths (i.e. SSE2 etc).  I probably can try
+to figure out the aus2 code to add that support, but since this system is going, there's little
+point in hacking anything.  (If someone disagrees with me, I'm interested in knowing why.)
+So what am I doing now?  Trying to convert our aus2 updating method to using balrog.   It's
+just that it's confusing and complicated as heck.
+I liken this to translating one language *I* don't know to another language that *I* also don't know.
+(i.e German -> Russian), except with the following items:
+* With AUS2, I have the final directories which the aus2 server serves the updates.  I opted to grab the paths and work with them to translate them(and the contents) to something Balrog understands.
+* Another option that I could've done was read the whole AUS2 code and understand that; but since we aren't even trying to understand how it serves updates (which is not the same as how Balrog serves updates), there's little point in doing that.
+* Translating the paths of what aus2 produces to what Balrog understand has been a very steep uphill climb, and with the decreasing cycles I can afford to deal with this, it has been slow going.
 ==== frg ====