Guide to porting extensions?

General discussion, compatibility and contributed extensions.

Moderators: satrow, Lootyhoof, FranklinDM

User avatar
moonbat
Lunatic
Lunatic
Posts: 376
Joined: 2015-12-09, 15:45
Location: Australia

Guide to porting extensions?

Unread post by moonbat » 2019-08-21, 03:06

I found and liked Pure URL from CAA, and contacted the author about porting it to PM. He said he doesn't use PM and was ok with others going ahead porting it. The extension is licensed under GPL.
Is there an existing post or guide on how to change install.rdf when repackaging an extension for PM? Can I add the modified extension here on the addons site after that?
"One hosts to look them up, one DNS to find them and in the darkness BIND them."

Linux Mint 19.2 Xfce x64 on HP i5 laptop with 4 GB RAM, always latest versions of PM & Basilisk unless specified.

vannilla
Astronaut
Astronaut
Posts: 625
Joined: 2018-05-05, 13:29

Re: Guide to porting extensions?

Unread post by vannilla » 2019-08-21, 11:40

To make it compatible with Pale Moon (or Basilisk) you have to add a "targetApplication" block with Pale Moon (or Basilisk)'s GUID. It's XML, so it shouldn't be too hard (even if all you do is copy and pasting.)
If it's licensed under the GPL there shouldn't be any problem distributing it, but personally I'd change the branding (name & icons) just in case.
Also you might want to check the stickied threads, like this one: viewtopic.php?f=19&t=16785

User avatar
New Tobin Paradigm
Off-Topic Sheriff
Off-Topic Sheriff
Posts: 5882
Joined: 2012-10-09, 19:37
Location: Sector 001

Re: Guide to porting extensions?

Unread post by New Tobin Paradigm » 2019-08-21, 11:54

You also should change the ID unless you can prove that the original developer has given you permission to take over the extension. Of course at that point you likely have permission to use the name and branding too ;)

We require this because half-ass forking an extension with an existing ID can be seen as a form of browser highjacking because an update request would pull the new version. This is why all submissions are checked against the 19 thousand or so known IDs from AMO by the Phoebus Software and rejected unless the Add-ons Team releases the ID.

User avatar
moonbat
Lunatic
Lunatic
Posts: 376
Joined: 2015-12-09, 15:45
Location: Australia

Re: Guide to porting extensions?

Unread post by moonbat » 2019-08-21, 13:45

vannilla wrote:
2019-08-21, 11:40
Also you might want to check the stickied threads, like this one: viewtopic.php?f=19&t=16785
Thanks, this is what I was looking for - thought it would be in the browser extensions forum :)
New Tobin Paradigm wrote:
2019-08-21, 11:54
You also should change the ID unless you can prove that the original developer has given you permission to take over the extension. Of course at that point you likely have permission to use the name and branding too ;)
Will Telegram chat transcript screenshots suffice? ;)
But yeah, makes sense, I'll see about changing the ID.
"One hosts to look them up, one DNS to find them and in the darkness BIND them."

Linux Mint 19.2 Xfce x64 on HP i5 laptop with 4 GB RAM, always latest versions of PM & Basilisk unless specified.

Post Reply