<gchristensen>
that wrapping is a bit weird, maybe if those were made in to relative dates it'd be more usable and use less space? I think there are good reasons to constrain widths but I'm no expert, just parroting what I think I've heard
MichaelRaskin has quit [Ping timeout: 240 seconds]
<qyliss>
there are good reasons to constrain widths of prose, yeah
<qyliss>
I don't think it applies to multi-column tables
rj has joined #nixos-dev
<qyliss>
Relative dates make it hard to see when things actually happened, and they can be misleading with rounding
<gchristensen>
yeah
<qyliss>
maybe I can put my money where my mouth is and make a PR
<qyliss>
everything else I wanted to do today is blocked on rebuilding stdenv anyway
<gchristensen>
(♥‿♥✿)
<qyliss>
I do want to improve my Perl...
<gchristensen>
I've found it fairly reasonable once I figured out how to write tests
<gchristensen>
I can't write valid perl without starting with tests
<qyliss>
I like what I've seen of Perl but I'm not confident in it
<gchristensen>
start with a test :)
<qyliss>
tbh I think we could probably just unconstrain every page on Hydra
<gchristensen>
I'll have to defer to samueldr on this
<qyliss>
it's all tables and preformatted text that would just scroll off to the side if it was width-constrained
tv has quit [Ping timeout: 260 seconds]
rj has quit [Remote host closed the connection]
rj has joined #nixos-dev
<cransom>
+1 on that. my web browser is on a portrait rotated monitor. anything left in the margins for me is wasted space, especially since it's already narrower than typical usage.
<gchristensen>
would love for an expert at this get involved
tv has joined #nixos-dev
tv has quit [Client Quit]
tv has joined #nixos-dev
orivej has quit [Ping timeout: 268 seconds]
MichaelRaskin has joined #nixos-dev
<MichaelRaskin>
Maybe people who care about font choice have force-overrides in the browser already
<qyliss>
The development version of Bootstrap has a bunch of different container sizes, so we could just change to a bigger one
<qyliss>
But the version we're using doesn't :(
<qyliss>
oh actually we'd just need to go up one minor version
AkechiShiro has joined #nixos-dev
justanotheruser has joined #nixos-dev
pmy has joined #nixos-dev
orivej has joined #nixos-dev
AlwaysLivid has quit [Ping timeout: 240 seconds]
kini has quit [Remote host closed the connection]
kini has joined #nixos-dev
mkaito has joined #nixos-dev
mkaito has joined #nixos-dev
kini has quit [Remote host closed the connection]
kini has joined #nixos-dev
cole-h has joined #nixos-dev
qyliss has quit [Quit: bye]
qyliss has joined #nixos-dev
<samueldr>
gchristensen: it's probably good to switch to container-fluid
<samueldr>
because yes, this is an *app* more than *contentful* web
<samueldr>
and if there is a place where constraining width helps, we can, at this location, add what is needed
<samueldr>
I don't see how it matters with what I was saying
<samueldr>
I know the current thing is to add unstable to `pname`
<samueldr>
and I'll do it because "it's how we do it"
<samueldr>
but it adds no value in a package which is a collection of firmware files that will never see a released version
<supersandro2000>
the current thing is to add unstable to version and to pname if there are two packages in nixpkgs
<supersandro2000>
but it needs a version :P
<samueldr>
sure, and the date is fine there
<samueldr>
but I don't see any value in adding unstable
<samueldr>
and it's clearly written
<samueldr>
>> If a package is not a release but a commit from a repository, then the version part of the name must be the date of that (fetched) commit. The date must be in "YYYY-MM-DD" format. Also append "unstable" to the name - e.g., "pkgname-unstable-2014-09-23".
<samueldr>
append unstable to the package name
<supersandro2000>
but the package has no release numbers and just using the date would imply it has
<supersandro2000>
samueldr: that sentence does not solve the question because it was written before pname + version
<sterni>
samueldr: just add unstable to version only
__monty__ has quit [Quit: leaving]
<sterni>
iirc pname = "something-unstable" just causes a lot of problems
<sterni>
(“problems” as in repology doesn't like it)
<supersandro2000>
so its ambiguous and people use pname for the package name all over the place which breaks if you change it to *-unstable
<supersandro2000>
also we would technically add and remove packages when changing pname and pname should match the attribute name
<samueldr>
then fix the documentation
<supersandro2000>
but nix is not smart enough to correctly parse unstable-XXXX-XX-XX in some functions
<supersandro2000>
samueldr: I could just push it straight to master and hope no one notices it
<samueldr>
no
<supersandro2000>
otherwise I need to get some more wood and nails
<supersandro2000>
and we need to build that bikesheed
<samueldr>
but again, I wrote YYYY-MM-DD for the version because we need a version, but it's not "unstable", so I don't think unstable adds any kind of value
<supersandro2000>
but YYYY-MM-DD is the version format of some programs who thought semver is "complicated" and we can't create version numbers for programs which do not exist
<samueldr>
I don't follow how that's relevant
<samueldr>
we're not doing maths with version number across unrelated packages
<supersandro2000>
If you set the version number to YYYY-MM-DD it implies that the packages has versioned releases
<samueldr>
but it's not even really a package, it's a derivation with "data"
<samueldr>
you won't be installing this
<samueldr>
it's a transient dependency
<samueldr>
if we had a way to not have them listed as packags, but present for callPackage dependency injection, it would be that
<evils>
supersandro2000: are you arguing an ISO8601 date on its own should only be used when upstream used that as a release name?
<evils>
s/release name/release version string/
<supersandro2000>
Can we make packages not installable?
<samueldr>
we don't even have a clear definition of "package" really
<supersandro2000>
evils: no, that is how it is.
<evils>
supersandro2000: there no defined "how it is" there's how mergers accept stuff
<supersandro2000>
but do you want to get that booting thingy done or continue talking about version numbers?
<supersandro2000>
evils: but isn't that the defacto standard?
<evils>
i don't think there is a defacto standard in this case
<evils>
i think a date string is a perfectly fine identifier for an arbitrary commit; sometimes i prefer a git short commit hash to identify a commit though
<samueldr>
anyway, I wanted to take the pulse of multiple contributors on *requiring* the "unstable" moniker without any judgement even if it brings no value
<samueldr>
but I'll continue working on my "boot thingy" instead
<samueldr>
as I don't think the discussion will be fruitful currently
<evils>
sorry if i disrupted the discussion by jumping in; i've been annoyed by this since it was suggested on a PR of mine 3 months ago and i consider it an impasse; but i haven't put serious thought into it
<supersandro2000>
evils: it is not allowed to reference git commits in fetches with short hashes
<evils>
supersandro2000: i meant using a git short commit as a version string; usually clearer that it's not an upstream endorsed release
<supersandro2000>
because you can brute force bad commit short shas using forks
<supersandro2000>
yeah, could be but changing everything is a bit of work I avoid for now
<evils>
to me: semver tag implies some stability, a date just says "it's whatever it was on this date" (as determined by the packager or upstream) and a git short commit has almost no meaning (besides implying that that commit isn't tagged) (though i do have a local change that uses a short commit hash of a tagged commit...)
<evils>
supersandro2000: ^ and good night :)
rj has quit [Ping timeout: 240 seconds]
<supersandro2000>
if pytest uses a format of date versioning it cannot be whatever was on that date
<supersandro2000>
otherwise it would be always broken
avocadoom has joined #nixos-dev
kini has quit [Remote host closed the connection]
kini has joined #nixos-dev
supersandro2000 has quit [Killed (kornbluth.freenode.net (Nickname regained by services))]