On Wed, Apr 29, 2020 at 7:04 PM Stephen John Smoogen <smooge(a)gmail.com> wrote:
On Wed, 29 Apr 2020 at 18:44, Miro Hrončok <mhroncok(a)redhat.com> wrote:
>
> On 29. 04. 20 21:42, Lloyd Kvam wrote:
> >> What you say is true. I still don't agree that "python3.9" as
a package name
> >> annoys humans.
> > I am not a package pro, but simply reading along as an interested human user. To
me, adding
> > periods in package names can be confusing.
>
> My sentence was about "python3.9" not being more annoying than
"python-3.9".
>
> I wonder, why do you consider periods in names confusing?
>
> We have around ~100 source package names with dot. Most of them have versions, e.g.:
>
> clang9.0
The standard confusing part is if you are used to seeing a . only in the version or
release parts.. you scan down and see
dotnet3.1-3.1.2-40
my usual mistake is where I do a stupid programming and do something like
ls -1 | awk '{split($0,a,"."); print a[1]}' | whatever I needed for
just the names of rpms
which for most packages will give me the Name-Ver[.sion removed]. it is lazy script
programming but it works often enough that my brain wants it to work all the time than
doing something like
ls -1 *rpm | xargs rpm --qf='%{NAME}\n' -qp | whatever i needed for just the
names of the rpms.
Splitting on the second to last dash of an rpm file name will *always*
give you the name on the left side, and the version-release on the
right side, so I usually do a split that way. :)
--
真実はいつも一つ!/ Always, there's only one truth!