Opened 4 years ago
Closed 3 years ago
#62714 closed update (fixed)
x265: consider changing upstream to bitbucket.org/multicoreware/x265_git
Reported by: | gaming-hacker (G Alexander) | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.6.4 |
Keywords: | Cc: | ||
Port: | x265 |
Description
Hello,
videolan site has old version of 3.4 and not updated to 3.5.
It's here
https://bitbucket.org/multicoreware/x265_git/wiki/Home
MD5 (x265_3.4.tar.gz) = e37b91c1c114f8815a3f46f039fe79b5
MD5 (x265_3.5.tar.gz) = deb5df5cb2ec17bdbae6ac6bbc3b1eef
does macports have bitbucket support? or have to do things old school git method?
Change History (8)
comment:1 Changed 4 years ago by kencu (Ken)
comment:2 Changed 4 years ago by gaming-hacker (G Alexander)
multicoreware is the author of x265, videolan just clones their repo once in a while
comment:3 Changed 4 years ago by gaming-hacker (G Alexander)
that patch file needs to be checked as well.
the patch is still needed.
comment:4 Changed 4 years ago by kencu (Ken)
Summary: | port x265 → port x265: consider changing upstream to bitbucket.org/multicoreware/x265_git |
---|
comment:5 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | nomaintainer removed |
---|---|
Keywords: | git bitbucket removed |
Summary: | port x265: consider changing upstream to bitbucket.org/multicoreware/x265_git → x265: consider changing upstream to bitbucket.org/multicoreware/x265_git |
comment:6 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to gaming-hacker:
MD5 (x265_3.4.tar.gz) = e37b91c1c114f8815a3f46f039fe79b5
MD5 (x265_3.5.tar.gz) = deb5df5cb2ec17bdbae6ac6bbc3b1eef
md5 is an obsolete hash algorithm that we don't want to use anymore.
does macports have bitbucket support? or have to do things old school git method?
Yes, MacPorts has a bitbucket portgroup that can be used to simplify getting things from bitbucket-hosted projects.
comment:7 Changed 3 years ago by gaming-hacker (G Alexander)
Thanks for the bitbucket info, I need to update my repo.
Please close.
comment:8 Changed 3 years ago by mascguy (Christopher Nielsen)
Resolution: | → fixed |
---|---|
Status: | new → closed |
which is the real one? We would probably want to use the exact same version that everyone in Repology uses, as that is the one that all the software will be built and tested against.