Please note that naming conventions of Java packages are just that; conventions. You can name them whatever you want. The only thing that is enforced is that a . delineates a subdirectory in the filesystem where the compiler looks for the source.
Also note that with gmail, at least, the . is ignored in the email. Therefore myname@gmail.com and my.name@gmail.com are equivalent. Because they are equivalent, com.gmail.myname would be an appropriate package name tied to such an email address.
The reason for using domain names/email addresses is that they are a convenient way to (probably) avoid namespace collisions for packages. However, with modern refactoring technology available in your local IDE, this should not be a blocker for progress. Choose a non-top-level-domain prefix and name your program or library whatever you want rogue.my.awesome.java.program.
Finally, note that naming your package something like com.google.myname implies that google developed the package. Most programmers, for this reason, put some amount of work into establishing some screen name or shortening of their actual name as an online presence so that they can use that as a prefix for this and similar projects: myname.awesome.java.program. This satisfies an elegant secondary concern of naming: knowing who to contact if, upon coming across the source, you have questions.