• 0 Posts
  • 43 Comments
Joined 1 year ago
cake
Cake day: June 26th, 2023

help-circle


  • Heres an example, ebuilds are named package-version.ebuild and that version in the filename is used to define variables (such as $P here which is the name-version) to make new versions as simple as copying the ebuild with the new version in the filename.

    use_enable is used to generate the --enable-(option) or --disable-(option) as set by the user.

    For more info, see the devmanual. They’re nice relatively straightforward bash like PKGBUILDs, but with the repetitious stuff taken out.

    # Copyright 1999-2022 Gentoo Authors
    # Distributed under the terms of the GNU General Public License v2
    
    EAPI=8
    
    DESCRIPTION="GNU charset conversion library for libc which doesn't implement it"
    HOMEPAGE="https://www.gnu.org/software/libiconv/"
    SRC_URI="ftp://ftp.gnu.org/pub/gnu/libiconv/${P}.tar.gz"
    
    LICENSE="LGPL-2+ GPL-3+"
    SLOT="0"
    KEYWORDS="~amd64 ~ppc ~sparc ~x86"
    IUSE="nls"
    
    RDEPEND="!sys-libs/glibc"
    DEPEND="${RDEPEND}"
    
    src_configure() {
    	econf $(use_enable nls)
    }
    









  • eh, its true if you want it to be signed by microsoft, which some projects have forked out for, buut it was put into the spec for x86_64 systems that users can replace the keys. so you can make your own keys, and if you want to dual boot add microsoft’s keys to the ok to boot list.

    one of the signed projects is a shim that lets you approve whatever you want more or less; pretty much everything that talks about MOK refers back to this shim. many distributions use this shim




  • package myself; I chose Gentoo (and previously Arch) in part because its reasonably easy to package things there.

    Most build systems are covered by eclasses ( libraries) that handle the repetitive minutia every package that build system needs.

    Here’s the tuba ebuild for example (from GURU, the Gentoo equivalent of the AUR), 90% of it is just listing the dependencies and telling it to use a few eclasses to handle everything else.

    Oh, and here’s the lemmy back end ebuild, the giant wall of crates is automatically generated/updated from a tool that reads the cargo files. (needed because Gentoo doesn’t allow internet access during the build for normal packages so crates are downloaded ahead of time)


  • It can be easy to be nose-blind to your own smell, trust me its easy to stink enough to be offensive to others but not notice yourself.

    They’re doing you a favor by letting you know. Just take the extra moment and put some on in the morning. Just don’t overdo it and douse yourself in body spray; too much body spray is nasty too.



  • its the internet, they are. Putting it behind cloudflare and locking down the firewall to only allow their ips has filtered out pretty much everything. its free and pretty straight forward if you own your own domain.

    check your nginx access logs, I’m sure they’re full of people poking it.

    134.122.30.157 - - [22/Jul/2023:07:45:28 -0500] "\x00\x00\x00\xB2\x9A\xD6\x8E\xCF.\x22\x83\xA9\xBF2\xBA|ro\xAE_\x95\xEC\x80\xE4\xE9n\x82q\x9E\xC6\xA9\x8F\xF5" 400 157 "-" "-"
    

    and all kinds of other obvious incorrect stuff when a normal request looks like

    2001:19f0:5c01:dd3:5400:2ff:feba:75b - - [27/Jul/2023:07:21:25 -0500] "GET /comment/165203 HTTP/2.0" 200 953 "-" "Lemmy/unknown version; +https://lemmy.xcoolgroup.com"
    

    GET/POST/WHATEVER /url …



  • lemmy can run on a decent variety of hardware, just has to be some thing left on 24/7 and exposed to the internet (be careful, the internet is a hostile place… mine was getting scanned and poked constantly until I put it behind cloudflare and then locked the firewall down to just let in cloudflare), and of course more users take more powerful hardware.

    For my personal just me instance though, I’m just running it on a Raspberry Pi 4 I run some other stuff on. Uses less than a gig of memory.