Re:Build2 – A C++ Build Toolchain and Package Manager
by Sanddancer on Friday May 05, 2017 @04:29AM
(#14271932)
Systems like Debian, though, have the ability to add custom repositories. So after the initial, possibly small package that just configures the sources.list, everything's handled with all the other updates. That's something that npm, etc, can't do.
Re:Build2 – A C++ Build Toolchain and Package Manager
by pathsjs on Friday May 05, 2017 @04:58AM
(#14272053)
Npm and many other package managers support custom repositories just fine
Re:Build2 – A C++ Build Toolchain and Package Manager
by paulddraper on Thursday May 04, 2017 @10:47PM
(#14270782)
Sure. I publish to deb repos all the time.
(I've found Bintray to be the easiest.)
Re:Build2 – A C++ Build Toolchain and Package Manager
by tyoverby on Friday May 05, 2017 @11:05AM
(#14273949)
I didn't say "a" deb repo, I said "the standard debian repository". Just like when I'm talking about NPM, I'm talking about the main NPM repository, not my company's private NPM server.
Re:Build2 – A C++ Build Toolchain and Package Manager
by paulddraper on Friday May 05, 2017 @11:28AM
(#14274141)
Well, you've chosen a terrible comparison then.
How many NPM repos are there? Just one, too-big-to-fail, centralized repository.
Don't ding apt/deb just because people setup their own repos rather than put all the code in the world into one bucket.
There's a lot more inconvenient things than adding the /etc/apt/sources
If you actually manage to get your library included, then we can compare how long it takes to update your library.