Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

netatalk: drop package #15873

Merged
merged 1 commit into from
Jun 15, 2021
Merged

netatalk: drop package #15873

merged 1 commit into from
Jun 15, 2021

Conversation

commodo
Copy link
Contributor

@commodo commodo commented Jun 15, 2021

Maintainer: me
Compile tested: n/a
Run tested: n/a


Link to abandoned packages PR: openwrt/packages-abandoned#18

AppleShare products have been unused for a while now (since Mac OS 9.2.2)
around 2002.
So, there should be fewer users requiring this package.

Last update of netatalk was in December 2018. Not sure if newer updates
will be created.

It's time to cut the cord on our end and move it to the abandoned packages.

Info: https://en.wikipedia.org/wiki/AppleShare

Signed-off-by: Alexandru Ardelean ardeleanalex@gmail.com

Link to abandoned packages PR: openwrt/packages-abandoned#18

AppleShare products have been unused for a while now (since Mac OS 9.2.2)
around 2002.
So, there should be fewer users requiring this package.

Last update of netatalk was in December 2018. Not sure if newer updates
will be created.

It's time to cut the cord on our end and move it to the abandoned packages.

Info: https://en.wikipedia.org/wiki/AppleShare

Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
@neheb neheb merged commit 261f368 into openwrt:master Jun 15, 2021
@commodo commodo deleted the netatalk-drop branch June 15, 2021 09:23
@mstorchak
Copy link
Contributor

Why removing a package if it still works?

@commodo
Copy link
Contributor Author

commodo commented Jun 16, 2021

Why removing a package if it still works?

well, this mostly has to do with me not wanting to maintain it anymore;
it was my decision as a maintainer to drop it, and not keep it around;
i also don't [just] want to remove myself as a maintainer and leave the package un-maintained :)
the whole idea in the packages feed is that all package should have at least one maintainer listed; to avoid packages being abandoned, but still present in the packages feed;

but, since you raised your voice here, this is good;
feel free to revert these 2 PRs and add yourself as a maintainer :)

@commodo
Copy link
Contributor Author

commodo commented Jun 17, 2021

Why removing a package if it still works?

well, this mostly has to do with me not wanting to maintain it anymore;
it was my decision as a maintainer to drop it, and not keep it around;
i also don't [just] want to remove myself as a maintainer and leave the package un-maintained :)
the whole idea in the packages feed is that all package should have at least one maintainer listed; to avoid packages being abandoned, but still present in the packages feed;

but, since you raised your voice here, this is good;
feel free to revert these 2 PRs and add yourself as a maintainer :)

ping;
so, my intent isn't to upset anyone;
i'm mostly trying to simplify my life a bit here :)
i.e. i don't want to bring this package back [and maintain it], but i am fine if someone else does it;

@mstorchak
Copy link
Contributor

@commodo , I apologize for the delay - got distracted and then forgot to reply in time.
No worries, I'll check how much I depend on netatalk and consider maintainership if it appears that this is the only option for TimeMachine backups for me.

@aparcar
Copy link
Member

aparcar commented Jan 23, 2022

ugh, bummer. How to use remote time machine backups in 2022?

@neheb
Copy link
Contributor

neheb commented Jan 24, 2022

thought samba could handle that.

@aparcar
Copy link
Member

aparcar commented Jan 24, 2022

Great thank you

@Chapoly1305
Copy link

@commodo thank you for the effort. As one of many user of using netatalk on home router, I found the news recently and I really appreciate for your commitment. Hopefully we can see this project enrolls the mainline later.

@commodo
Copy link
Contributor Author

commodo commented Nov 19, 2023

@commodo thank you for the effort. As one of many user of using netatalk on home router, I found the news recently and I really appreciate for your commitment. Hopefully we can see this project enrolls the mainline later.

Well, you can jump in to take it over :)

One reason (from me) to drop it, was to also allow for someone else to take it over.

@APCCV
Copy link
Contributor

APCCV commented May 15, 2024

@commodo well, it may be me.

It looks like I will need netatalk for a while (MacOS 10.13 and earlier cannot use TimeMachine to a SMB share). I was also surprised when I did not see the package around anymore.

I got netatalk 3.1.18-3 to build for ipq806x. It seems to work; one old Mac is TimeMachining to it now.

How do I take over? Put in a PR for it to go back in?

@APCCV
Copy link
Contributor

APCCV commented Nov 6, 2024

For the history:

That shows how something that could have been done with three PRs by someone that knew what they were doing, took 4x more.

It’s done. Next release will have netatalk and AppleTalk.

@Neustradamus, do you use this thing? Asking as It’s always good to know you’re not alone in this world. Any details you can share how you use netatalk on openwrt? Anything in particular to enable? Next release I’ll try get a skinny package and a couple of more functionally rich ones in place… which means next commit I push is probably going to take some churn.

@aparcar
Copy link
Member

aparcar commented Nov 6, 2024

I'm using this thing for quite some time, works nice. You're not alone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants